Disqus Comment System < 2.76 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.76
- Affected Plugin
- Disqus Comment System
- Affected Version
< 2.76- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2014-5347
At a glance
CVE-2014-5347 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Disqus Comment System WordPress plugin, affecting versions < 2.76. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.76; sites on affected versions should update now. Disclosed August 2014, reported by Nik Cubrilovic.
Vulnerability Overview
Multiple cross-site request forgery (CSRF) vulnerabilities in the Disqus Comment System plugin before 2.76 for WordPress allow remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS) attacks via the (1) disqus_replace, (2) disqus_public_key, or (3) disqus_secret_key parameter to wp-admin/edit-comments.php in manage.php or that (4) reset or (5) delete plugin options via the reset parameter to wp-admin/edit-comments.php.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Disqus Comment System < 2.76 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 Disqus Comment System the fix is 2.76: builds < 2.76 are affected, anything from 2.76 onward is not.
Remediation
Update to version 2.76, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Disqus Comment System: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Disqus Comment System 2.76 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C