Acunetix WP Security <= 4.0.4 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 4.0.5
- Affected Plugin
- Acunetix WP Security
- Affected Version
< 4.0.5- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Acunetix WP Security WordPress plugin, affecting versions < 4.0.5. 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 4.0.5; sites on affected versions should update now. Disclosed February 2014, reported by Yashar Shahinzadeh.
Vulnerability Overview
The Acunetix WP Security plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.0.4. This is due to missing or incorrect nonce validation in the ~/box-database-backup.php file. This makes it possible for unauthenticated attackers to trigger a database back-up 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 confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Acunetix WP Security < 4.0.5 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 Acunetix WP Security the fix is 4.0.5: builds < 4.0.5 are affected, anything from 4.0.5 onward is not.
Remediation
Update to version 4.0.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Acunetix WP Security: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Acunetix WP Security 4.0.5 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