CVE-2025-14167
CSRF Vulnerability in Remove Post Type Slug WordPress Plugin
Publication date: 2026-02-19
Last updated on: 2026-02-19
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| remove_post_type_slug | remove_post_type_slug | to 1.0.2 (inc) |
| remove_post_type_slug | plugin | to 1.0.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Remove Post Type Slug plugin for WordPress has a vulnerability known as Cross-Site Request Forgery (CSRF) in all versions up to and including 1.0.2. This vulnerability arises because the plugin uses incorrect nonce validation logic that employs an OR (||) operator instead of an AND (&&) operator. As a result, the validation fails improperly when the nonce field is not empty or when verification fails, instead of failing only when the nonce is empty and verification fails. This flaw allows an attacker to trick a site administrator into performing an action, such as clicking a malicious link, which then enables the attacker to modify the plugin's post type slug removal settings without proper authorization.
How can this vulnerability impact me? :
This vulnerability can allow an unauthenticated attacker to change the settings of the Remove Post Type Slug plugin by tricking an administrator into performing an action. Such unauthorized modifications could lead to unexpected behavior on the WordPress site, potentially affecting how URLs are handled or displayed. While the vulnerability does not directly compromise confidentiality or availability, it can lead to integrity issues by allowing unauthorized changes to plugin settings.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know