Crowdsignal Dashboard < 2.0.21 - Cross-Site Request Forgery

2013-11-06 00:00

Strategic Overview

Status: Patched in 2.0.21
Affected Plugin: Crowdsignal Dashboard – Polls, Surveys & more
Affected Version: < 2.0.21
CVSS: 7.1High
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE pending

View all Crowdsignal Dashboard – Polls, Surveys & more vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Crowdsignal Dashboard WordPress plugin, affecting versions < 2.0.21. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.21; sites on affected versions should update now. Disclosed November 2013.

Vulnerability Overview

The Crowdsignal Dashboard – Polls, Surveys & more plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions before 2.0.21. This is due to missing or incorrect nonce validation in the rating_settings function. This makes it possible for unauthenticated attackers to have an unknown impact via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Crowdsignal Dashboard < 2.0.21 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 Crowdsignal Dashboard the fix is 2.0.21: builds < 2.0.21 are affected, anything from 2.0.21 onward is not.

Remediation

Update to version 2.0.21, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Crowdsignal Dashboard: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Crowdsignal Dashboard 2.0.21 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/683e10af-5414-4959-9823-93e88e84bb1b

Related records

Same weakness class

Other vulnerabilities in Crowdsignal Dashboard – Polls, Surveys & more

CVSS Vector

7.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityLow

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/