Skip to content
Laskyr

Plugins · remove-post-type-slug · data as of 2026-11-04

Is Remove Post Type Slug safe? Known vulnerabilities and latest version

Remove Post Type Slug is closed on wordpress.org

Closed on 2026-02-17 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you.

Status
Closed 2026-02-17
Known issues on record
1
Unpatched in latest
0

What to do

  1. Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
  3. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate remove-post-type-slug && wp plugin delete remove-post-type-slug

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. 1 record(s) do not state which versions are affected.

medium 4.3 CVE-2025-14167 · published 2026-02-19

Cross-site request forgery (CSRF) in Remove Post Type Slug (1.0.2 and older)

Affected
1.0.2 and older
Fixed in
unknown
Access needed (per CVSS)
No login needed; 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 Remove Post Type Slug plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.2. This is due to incorrect nonce validation logic that uses OR (||) instead of AND (&&), causing the validation to fail when the nonce field is not empty OR when verification fails, rather than when it's empty AND verification fails. This makes it possible for unauthenticated attackers to modify the plugin's post type slug removal settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

NVD CVE-2025-14167Wordfence advisoryPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Remove Post Type Slug vulnerability status badge
<a href="https://laskyr.com/plugins/remove-post-type-slug"><img src="https://laskyr.com/plugins/remove-post-type-slug/badge.svg" alt="Remove Post Type Slug 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