Settings modification via missing CSRF nonce validation
Published Jun 5, 2023 · Updated Nov 22, 2024
CSRF in Angrybyte WordPress Exit Box Lite 1.06 allows remote attackers to alter exit-box settings through an administrator's session. The exit_box_admin settings handler accepted POST data whenever xx was present without verifying an action-specific WordPress nonce; the patch adds check_admin_referer and emits the matching nonce in the form. Exploitation requires a logged-in administrator to submit an attacker-induced request, and the demonstrated consequence is unauthorized modification of plugin settings.
Summary
What happened
CSRF in Angrybyte WordPress Exit Box Lite 1.06 allows remote attackers to alter exit-box settings through an administrator's session. The exit_box_admin settings handler accepted POST data whenever xx was present without verifying an action-specific WordPress nonce; the patch adds check_admin_referer and emits the matching nonce in the form. Exploitation requires a logged-in administrator to submit an attacker-induced request, and the demonstrated consequence is unauthorized modification of plugin settings.
The record
- CVE
- CVE-2013-10029
- Published
- Jun 5, 2023
- Updated
- Nov 22, 2024
- Vendor
- Angrybyte
- Product
- WordPress Exit Box Lite
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 5, 2023CVE publishedPublication date reported by the CVE source.
- Nov 22, 2024Record 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=1.06
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.
Weakness, pattern, technique
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