Skip to content
Laskyr

Plugins · same-category-posts · data as of 2026-11-04

Is Same Category Posts safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (1.2.1)

As of 2026-11-04. 1 issue is on record for older versions; version 1.1.20 or newer fixes all of them that state a fix.

Latest version
1.2.1
Last updated
2026-09-23
Active installs
3,000+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.2+

Show posts related to the current category or other custom post types. — by Daniel Floeter

What to do

  1. Update to the latest version (1.2.1). Anything older than 1.1.20 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get same-category-posts --field=version shows what you run; wp plugin update same-category-posts updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.4 CVE-2025-14797 · published 2026-01-24

Stored cross-site scripting (XSS) in Same Category Posts (1.1.19 and older)

Affected
1.1.19 and older
Fixed in
1.1.20 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Same Category Posts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the widget title placeholder functionality in all versions up to, and including, 1.1.19. This is due to the use of `htmlspecialchars_decode()` on taxonomy term names before output, which decodes HTML entities that WordPress intentionally encodes for safety. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2025-14797Wordfence advisoryCode change (fix)Plugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Same Category Posts vulnerability status badge
<a href="https://laskyr.com/plugins/same-category-posts"><img src="https://laskyr.com/plugins/same-category-posts/badge.svg" alt="Same Category Posts vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit