DeBounce Email Validator <= 5.8.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 5.8.1
- Affected Plugin
- DeBounce Email Validator
- Affected Version
<= 5.8.0- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-13339
At a glance
CVE-2024-13339 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the DeBounce Email Validator WordPress plugin, affecting versions <= 5.8.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.8.1; sites on affected versions should update now. Disclosed February 2025, reported by SOPROBRO.
Vulnerability Overview
The DeBounce Email Validator plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.8.0. This is due to missing or incorrect nonce validation on the 'debounce_email_validator' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts 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.
CWE-352: Cross-Site Request Forgery (CSRF)
DeBounce Email Validator <= 5.8.0 carries this weakness at debounce_email_validator, 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 DeBounce Email Validator the fix is 5.8.1: builds <= 5.8.0 are affected, anything from 5.8.1 onward is not.
Remediation
Update to version 5.8.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to DeBounce Email Validator: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: DeBounce Email Validator 5.8.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in DeBounce Email Validator
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C