WordPress xmlrpc.php security bypass

wordpress-xmlrpc-security-bypass (33470) The risk level is classified as MediumMedium Risk

Description:

WordPress could allow a remote authenticated attacker to bypass security restrictions, caused by improper validation by the xmlrpc.php script. A remote attacker with contributor permissions could exploit this vulnerability to publish posts to the Web site.

Platforms Affected:

  • Debian, Debian Linux 4.0
  • WordPress, WordPress 2.1.2

Remedy:

Upgrade to the latest version of WordPress (2.1.3 or later), available from the WordPress Web site. See References.

For Debian GNU/Linux (wordpress):
Refer to DSA-1285-1 for patch, upgrade, or suggested workaround information. See References.

For other distributions:
Contact your vendor for upgrade or patch information.

Consequences:

Bypass Security

References:

  • Full-Disclosure Mailing List, Thu Apr 05 2007 - 17:49:15 CDT, Wordpress 2.1.2 xmlrpc Vulnerabilities at http://archives.neohapsis.com/archives/fulldisclosure/2007-04/0248.html.
  • WordPress Web site, WordPress at http://wordpress.org/.
  • CVE-2007-1893: xmlrpc (xmlrpc.php) in WordPress 2.1.2, and probably earlier, allows remote authenticated users with the contributor role to bypass intended access restrictions and invoke the publish_posts functionality, which can be used to publish a previously saved post.
  • DSA-1285: wordpress -- several vulnerabilities
  • SA24751: WordPress XML-RPC SQL Injection and Security Bypass
  • VUPEN/ADV-2007-1245: WordPress XML-RPC Module Remote SQL Injection and Security Bypass Vulnerabilities

Reported:

Apr 05, 2007

The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

For corrections or additions please email xforce@iss.net

Return to the main page