Stored script injection via missing settings nonce
Published Feb 19, 2025 · Updated Apr 8, 2026
CSRF in DeBounce Email Validator 5.8.0 and earlier allows remote attackers to store malicious scripts through a forged settings request. The debounce_email_validator settings page accepts configuration updates without correctly validating a WordPress nonce, allowing attacker-supplied script content to persist. Exploitation requires an administrator to trigger the forged request, after which the injected script executes when affected content is viewed in a browser.
Summary
What happened
CSRF in DeBounce Email Validator 5.8.0 and earlier allows remote attackers to store malicious scripts through a forged settings request. The debounce_email_validator settings page accepts configuration updates without correctly validating a WordPress nonce, allowing attacker-supplied script content to persist. Exploitation requires an administrator to trigger the forged request, after which the injected script executes when affected content is viewed in a browser.
The record
- CVE
- CVE-2024-13339
- Published
- Feb 19, 2025
- Updated
- Apr 8, 2026
- Vendor
- DeBounce
- Product
- DeBounce Email Validator
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=5.8.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo