Reset <= 1.6 - Cross-Site Request Forgery to Database Reset
Strategic Overview
- Status
- Patched in 1.7
- Affected Plugin
- Reset – WordPress Database Reset Plugin
- Affected Version
<= 1.6- CVSS
- 8.1High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-13684
At a glance
CVE-2024-13684 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Reset WordPress plugin, affecting versions <= 1.6. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.7; sites on affected versions should update now. Disclosed February 2025, reported by lucky_buddy.
Vulnerability Overview
The Reset plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6. This is due to missing or incorrect nonce validation on the reset_db_page() function. This makes it possible for unauthenticated attackers to reset several tables in the database like comments, themes, plugins, and more 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 integrity, availability.
CWE-352: Cross-Site Request Forgery (CSRF)
Reset <= 1.6 carries this weakness at reset_db_page(), 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 Reset the fix is 1.7: builds <= 1.6 are affected, anything from 1.7 onward is not.
Remediation
Update to version 1.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Reset: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Reset 1.7 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