Change Table Prefix <= 2.0 - Cross-Site Request Forgery via change_prefix_form
Strategic Overview
- Status
- Patched in 3.0
- Affected Plugin
- Change Table Prefix
- Affected Version
<= 2.0- CVSS
- 7.1High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-25932
At a glance
CVE-2024-25932 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Change Table Prefix WordPress plugin, affecting versions <= 2.0. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. The issue is fixed in version 3.0; sites on affected versions should update now. Disclosed February 2024, reported by Nguyen Xuan Chien.
Vulnerability Overview
The Change Table Prefix plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0. This is due to missing or incorrect nonce validation on the 'change_prefix_form' function. This makes it possible for unauthenticated attackers to toggle maintenance mode via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 availability.
CWE-352: Cross-Site Request Forgery (CSRF)
Change Table Prefix <= 2.0 carries this weakness at change_prefix_form, and reaching it 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 Change Table Prefix the fix is 3.0: builds <= 2.0 are affected, anything from 3.0 onward is not.
Remediation
Update to version 3.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Change Table Prefix: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Change Table Prefix 3.0 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