Admin settings change via CSRF
Published Jun 6, 2022 · Updated Aug 3, 2024
Cross-site request forgery in 2code Discy before 5.2 allows remote attackers to change administrator settings via crafted AJAX requests. Discy AJAX actions update theme options without validating a CSRF token, so a logged-in administrator's browser can be induced to submit changes such as payment-method settings. Exploitation requires the administrator to be authenticated and to interact with attacker-controlled content; the documented impact is unauthorized integrity modification of theme settings.
Summary
What happened
Cross-site request forgery in 2code Discy before 5.2 allows remote attackers to change administrator settings via crafted AJAX requests. Discy AJAX actions update theme options without validating a CSRF token, so a logged-in administrator's browser can be induced to submit changes such as payment-method settings. Exploitation requires the administrator to be authenticated and to interact with attacker-controlled content; the documented impact is unauthorized integrity modification of theme settings.
The record
- CVE
- CVE-2022-1421
- Published
- Jun 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- 2code
- Product
- Discy – Social Questions and Answers WordPress Theme
- Classifications
- CWE-352, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=5.2 <5.2
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