CVE-2007-0233

WordPress Core < 2.0.7 - SQL Injection

2007-01-15 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0.7
Affected Core
WordPress 2.0
Affected Version
<= 2.0.6
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2007-0233
View all WordPress 2.0 vulnerabilities

At a glance

CVE-2007-0233 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WordPress 2.0 WordPress release line, affecting <= 2.0.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.0.7; sites on affected versions should update now. Disclosed January 2007.

Vulnerability Overview

wp-trackback.php in WordPress 2.0.6 and earlier does not properly unset variables when the input data includes a numeric parameter with a value matching an alphanumeric parameter's hash value, which allows remote attackers to execute arbitrary SQL commands via the tb_id parameter. NOTE: it could be argued that this vulnerability is due to a bug in the unset PHP command (CVE-2006-3017) and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in WordPress.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in WordPress 2.0 <= 2.0.6 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WordPress 2.0 the fix is 2.0.7: builds <= 2.0.6 are affected, anything from 2.0.7 onward is not.

Remediation

Update to version 2.0.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress 2.0: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 2.0.7 is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2007-0233https://www.wordfence.com/threat-intel/vulnerabilities/id/c3b42bd3-f7d3-43d1-bdd8-4389fd82e1e9https://nvd.nist.gov/vuln/detail/CVE-2007-0233

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C