Disqus Comment System up to 2.39 reset cross-site request forgery

Summaryinfo

A vulnerability labeled as problematic has been found in Disqus Comment System up to 2.39. This issue affects some unknown processing. The manipulation of the argument reset results in cross-site request forgery. This vulnerability was named CVE-2014-5347. The attack may be performed from remote. In addition, an exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical has been found in Disqus Comment System up to 2.39. Affected is an unknown part. The manipulation of the argument reset with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The weakness was presented 08/19/2014 (Website). The advisory is shared for download at wordpress.org. This vulnerability is traded as CVE-2014-5347 since 08/19/2014. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details and a public exploit are known.

A public exploit has been developed by Nik Cubrilovic and been published before and not just after the advisory. The exploit is shared for download at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 2.40 eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (95288), Exploit-DB (34336) and SecurityFocus (BID 69205†). See VDB-70666 for similar entry. Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Disqus

Name

• Comment System

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30
• 2.31
• 2.32
• 2.33
• 2.34
• 2.35
• 2.36
• 2.37
• 2.38
• 2.39

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion