WordPress security changelog
MEDIUM CVE-2012-1936 Modified

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
May 03, 2012
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

The wp_create_nonce function in wp-includes/pluggable.php in WordPress 3.3.1 and earlier associates a nonce with a user account instead of a user session, which might make it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks on specific actions and objects by sniffing the network, as demonstrated by attacks against the wp-admin/admin-ajax.php and wp-admin/user-new.php scripts. NOTE: the vendor reportedly disputes the significance of this issue because wp_create_nonce operates as intended, even if it is arguably inconsistent with certain CSRF protection details advocated by external organizations

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

References

Primary and upstream sources