WordPress component: Cross-site request forgery

WordPress component is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 6.8 CVSS · cve@mitre.org

NVD score 6.8 CVSS 2.0 · nvd@nist.gov

Component: WordPress component
Plugin slug: Not applicable
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Aug 18, 2014
Weakness: CWE-352 — Cross-Site Request Forgery (CSRF)

What to do

Update, patch or deactivate.

Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

wp-includes/pluggable.php in WordPress before 3.9.2 does not use delimiters during concatenation of action values and uid values in CSRF tokens, which makes it easier for remote attackers to bypass a CSRF protection mechanism via a brute-force attack.

NVD vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Update, patch or deactivate.

Technical description

Primary and upstream sources