Unauthorized follow-state changes via missing AJAX nonces
Published Jul 3, 2024 · Updated Aug 1, 2024
CSRF in 2code WPQA Builder before 6.1.1 allows remote attackers to change a logged-in user's category and tag follows via forged requests. The wpqa_follow_cat and wpqa_unfollow_cat AJAX actions accept forged POST requests without validating a CSRF nonce. Exploitation requires a logged-in user to open attacker-controlled content, after which the user's category or tag follow state can be changed.
Summary
What happened
CSRF in 2code WPQA Builder before 6.1.1 allows remote attackers to change a logged-in user's category and tag follows via forged requests. The wpqa_follow_cat and wpqa_unfollow_cat AJAX actions accept forged POST requests without validating a CSRF nonce. Exploitation requires a logged-in user to open attacker-controlled content, after which the user's category or tag follow state can be changed.
The record
- CVE
- CVE-2024-2376
- Published
- Jul 3, 2024
- Updated
- Aug 1, 2024
- Vendor
- 2code
- Product
- WPQA Builder
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=0 <6.1.1
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
- WPScan forged AJAX request proof of conceptproof of concept · validated
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