CVE-2025-14167 MEDIUM

CVE-2025-14167: Remove Post Type Slug <= 1.0.2 - Cross-Site Request Forgery to Settings Update

Vendor Akshayshah5189
Product Remove Post Type Slug
Weakness CWE-352 · CSRF
Published February 19, 2026
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The Remove Post Type Slug plugin for WordPress contains a cross-site request forgery (CSRF) vulnerability in versions up to 1.0.2. An attacker can craft a malicious link or webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without the administrator's knowledge or consent. The vulnerability requires user interaction but does not require authentication.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into performing unwanted actions via a malicious link or webpage.

Potential impact on your site

04Site Impact

An attacker can modify site settings or data if an admin is tricked into visiting a malicious page.

Conditions required to exploit

05Prerequisites

Admin must visit attacker-controlled page or click a malicious link while logged into WordPress.

Key dates

06Disclosure timeline

February 19, 2026 CVE published
April 8, 2026 Record updated