medium
4
CWE
264
Advisory Published
Updated

CVE-2012-4421

First published: Fri Sep 14 2012(Updated: )

The create_post function in wp-includes/class-wp-atom-server.php in WordPress before 3.4.2 does not perform a capability check, which allows remote authenticated users to bypass intended access restrictions and publish new posts by leveraging the Contributor role and using the Atom Publishing Protocol (aka AtomPub) feature.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
WordPress<=3.4.1
WordPress=0.71
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.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
WordPress=3.2.1
WordPress=3.3
WordPress=3.3.1
WordPress=3.3.2
WordPress=3.3.3
WordPress=3.4.0

Remedy

http://core.trac.wordpress.org/changeset?old_path=%2Ftags%2F3.4.1&old=21780&new_path=%2Ftags%2F3.4.2&new=21780#file2

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-4421?

    The severity of CVE-2012-4421 is considered high due to its potential for privilege escalation.

  • How do I fix CVE-2012-4421?

    To fix CVE-2012-4421, upgrade to WordPress version 3.4.2 or later.

  • What systems are affected by CVE-2012-4421?

    CVE-2012-4421 affects WordPress versions prior to 3.4.2, as well as several earlier versions.

  • What types of attacks are associated with CVE-2012-4421?

    CVE-2012-4421 can allow remote authenticated users to bypass access restrictions and publish posts.

  • Who is most at risk due to CVE-2012-4421?

    Users with the Contributor role in WordPress installations prior to version 3.4.2 are most at risk.

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