medium
6.8
CWE
352
Advisory Published
Updated

CVE-2012-1936: CSRF

First published: Thu May 03 2012(Updated: )

** DISPUTED ** 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.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
WordPress<=3.3.1
WordPress=1.0
WordPress=1.0.1
WordPress=1.0.2
WordPress=1.1.1
WordPress=1.2
WordPress=1.2.1
WordPress=1.2.2
WordPress=1.2.3
WordPress=1.2.4
WordPress=1.2.5
WordPress=1.2.5-a
WordPress=1.3
WordPress=1.3.2
WordPress=1.3.3
WordPress=1.5
WordPress=1.5.1
WordPress=1.5.1.1
WordPress=1.5.1.2
WordPress=1.5.1.3
WordPress=1.5.2
WordPress=2.0
WordPress=2.0.1
WordPress=2.0.2
WordPress=2.0.4
WordPress=2.0.5
WordPress=2.0.6
WordPress=2.0.7
WordPress=2.0.8
WordPress=2.0.9
WordPress=2.0.10
WordPress=2.0.11
WordPress=2.1
WordPress=2.1.1
WordPress=2.1.2
WordPress=2.1.3
WordPress=2.2
WordPress=2.2.1
WordPress=2.2.2
WordPress=2.2.3
WordPress=2.3
WordPress=2.3.1
WordPress=2.3.2
WordPress=2.3.3
WordPress=2.5
WordPress=2.5.1
WordPress=2.6
WordPress=2.6.1
WordPress=2.6.2
WordPress=2.6.3
WordPress=2.6.5
WordPress=2.7
WordPress=2.7.1
WordPress=2.8
WordPress=2.8.1
WordPress=2.8.2
WordPress=2.8.3
WordPress=2.8.4
WordPress=2.8.4-a
WordPress=2.8.5
WordPress=2.8.5.1
WordPress=2.8.5.2
WordPress=2.8.6
WordPress=2.9
WordPress=2.9.1
WordPress=2.9.1.1
WordPress=2.9.2
WordPress=3.0
WordPress=3.0.1
WordPress=3.0.2
WordPress=3.0.3
WordPress=3.0.3
WordPress=3.0.4
WordPress=3.0.5
WordPress=3.0.6
WordPress=3.1
WordPress=3.1.1
WordPress=3.1.2
WordPress=3.1.3
WordPress=3.1.4
WordPress=3.2-beta1
WordPress=3.2.1
WordPress=3.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2012-1936?

    CVE-2012-1936 is considered a medium severity vulnerability due to its potential to facilitate cross-site request forgery (CSRF) attacks.

  • How do I fix CVE-2012-1936?

    To mitigate CVE-2012-1936, upgrade to a patched version of WordPress that is later than 3.3.1.

  • What software is affected by CVE-2012-1936?

    CVE-2012-1936 affects WordPress versions 3.3.1 and earlier, along with several earlier versions.

  • What attacks can CVE-2012-1936 enable?

    CVE-2012-1936 can enable remote attackers to conduct cross-site request forgery (CSRF) attacks on authenticated user actions.

  • Is CVE-2012-1936 still a risk if I have updated my WordPress?

    If you have updated your WordPress to a version later than 3.3.1, the risk associated with CVE-2012-1936 should be mitigated.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203