CVE-2007-6318: SQL Injection
Published Dec 12, 2007
·Updated
SQL injection vulnerability in wp-includes/query.php in WordPress 2.3.1 and earlier allows remote attackers to execute arbitrary SQL commands via the s parameter, when DBCHARSET is set to (1) Big5, (2) GBK, or possibly other character set encodings that support a "\" in a multibyte character.
Affected Software
24 affected components
WordPress=2.0
WordPress=2.0.1
WordPress=2.0.2
WordPress=2.0.3
WordPress=2.0.4
WordPress=2.0.5
WordPress=2.0.6
WordPress=2.0.7
WordPress=2.0.10
WordPress=2.0.10_rc1
WordPress=2.0.10_rc2
WordPress=2.1.1
WordPress=2.1.2
WordPress=2.1.3
WordPress=2.1.3_rc1
WordPress=2.1.3_rc2
WordPress=2.2
WordPress=2.2.1
WordPress=2.2.2
WordPress=2.2.3
WordPress=2.2_revision5002
WordPress=2.2_revision5003
WordPress=2.3
WordPress=2.3.1
Event History
Dec 12, 2007
CVE Published
12:46 AM
CVE Published
via MITRE·05:00 AM
Data Sourced
via MITRE·05:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2007-6318?
CVE-2007-6318 has been classified as a critical SQL injection vulnerability.
2
How do I fix CVE-2007-6318?
To fix CVE-2007-6318, update your WordPress installation to version 2.3.2 or later.
3
Which versions of WordPress are affected by CVE-2007-6318?
CVE-2007-6318 affects WordPress versions 2.3.1 and earlier.
4
What can attackers do with CVE-2007-6318?
Attackers can exploit CVE-2007-6318 to execute arbitrary SQL commands on the database.
5
Is CVE-2007-6318 specific to certain character sets?
Yes, CVE-2007-6318 is particularly problematic for databases where DB_CHARSET is set to Big5 or GBK.