Spam Protect for Contact Form 7 <= 1.2.9 - Authenticated (Editor+) Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 1.2.10
- Affected Plugin
- Spam Protect for Contact Form 7
- Affected Version
<= 1.2.9- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-32496
At a glance
CVE-2026-32496 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Spam Protect for Contact Form 7 WordPress plugin, affecting versions <= 1.2.9. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 1.2.10; sites on affected versions should update now. Disclosed March 2026, reported by andrea bocchetti.
Vulnerability Overview
The Spam Protect for Contact Form 7 plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in all versions up to, and including, 1.2.9. This makes it possible for authenticated attackers, with Editor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
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 interaction from a victim user. A successful exploit has high impact on integrity, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Spam Protect for Contact Form 7 <= 1.2.9 takes an account at Editor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Spam Protect for Contact Form 7 the fix is 1.2.10: builds <= 1.2.9 are affected, anything from 1.2.10 onward is not.
Remediation
Update to version 1.2.10, or a newer patched version
How does WordSec protect against this?
An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Spam Protect for Contact Form 7 1.2.10 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Spam Protect for Contact Form 7
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C