Discy <= 5.1 - Cross-Site Request Forgery to Settings Update
Strategic Overview
- Status
- Patched in 5.2
- Affected Theme
- Discy - Social Questions and Answers WordPress Theme
- Affected Version
< 5.2- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-1421
At a glance
CVE-2022-1421 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Discy - Social Questions and Answers WordPress Theme WordPress theme, affecting versions < 5.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.2; sites on affected versions should update now. Disclosed May 2022, reported by Bibek Neupane.
Vulnerability Overview
The Discy WordPress theme before 5.2 lacks CSRF checks in some AJAX actions, allowing an attacker to make a logged in admin change arbitrary 's settings including payment methods via a CSRF attack
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Discy - Social Questions and Answers WordPress Theme < 5.2 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 Discy - Social Questions and Answers WordPress Theme the fix is 5.2: builds < 5.2 are affected, anything from 5.2 onward is not.
Remediation
Update to version 5.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Discy - Social Questions and Answers WordPress Theme: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Discy - Social Questions and Answers WordPress Theme 5.2 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Discy - Social Questions and Answers WordPress Theme
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C