Remove CPT base <= 5.8 - Cross-Site Request Forgery to CPT base deletion
Strategic Overview
- Status
- Patched in 5.9
- Affected Plugin
- Remove CPT base
- Affected Version
<= 5.8- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-29431
At a glance
CVE-2022-29431 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Remove CPT base WordPress plugin, affecting versions <= 5.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.9; sites on affected versions should update now. Disclosed May 2022, reported by R3N0.
Vulnerability Overview
Cross-Site Request Forgery (CSRF) vulnerability in KubiQ CPT base plugin <= 5.8 at WordPress allows an attacker to delete the CPT base.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Remove CPT base <= 5.8 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Remove CPT base the fix is 5.9: builds <= 5.8 are affected, anything from 5.9 onward is not.
Remediation
Update to version 5.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Remove CPT base: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Remove CPT base 5.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C