CVE-2007-6318: SQL Injection
First published: Wed 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 DB_CHARSET is set to (1) Big5, (2) GBK, or possibly other character set encodings that support a "\" in a multibyte character.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| 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 |
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.
Reference Links
- http://lists.grok.org.uk/pipermail/full-disclosure/2007-December/058999.html
- http://secunia.com/advisories/28005
- http://secunia.com/advisories/28310
- http://securityreason.com/securityalert/3433
- http://www.abelcheung.org/advisory/20071210-wordpress-charset.txt
- http://www.securityfocus.com/archive/1/484828/100/0/threaded
- http://www.securityfocus.com/bid/26795
- http://www.securitytracker.com/id?1019071
- http://www.vupen.com/english/advisories/2007/4172
- https://exchange.xforce.ibmcloud.com/vulnerabilities/38959
- https://www.redhat.com/archives/fedora-package-announce/2008-January/msg00079.html
- https://www.redhat.com/archives/fedora-package-announce/2008-January/msg00098.html
Frequently Asked Questions
What is the severity of CVE-2007-6318?
CVE-2007-6318 has been classified as a critical SQL injection vulnerability.
How do I fix CVE-2007-6318?
To fix CVE-2007-6318, update your WordPress installation to version 2.3.2 or later.
Which versions of WordPress are affected by CVE-2007-6318?
CVE-2007-6318 affects WordPress versions 2.3.1 and earlier.
What can attackers do with CVE-2007-6318?
Attackers can exploit CVE-2007-6318 to execute arbitrary SQL commands on the database.
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.
- agent/references
- agent/type
- agent/softwarecombine
- agent/author
- agent/severity
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/wordpress
- canonical/wordpress
- version/wordpress/2.0
- version/wordpress/2.0.1
- version/wordpress/2.0.2
- version/wordpress/2.0.3
- version/wordpress/2.0.4
- version/wordpress/2.0.5
- version/wordpress/2.0.6
- version/wordpress/2.0.7
- version/wordpress/2.0.10
- version/wordpress/2.0.10_rc1
- version/wordpress/2.0.10_rc2
- version/wordpress/2.1.1
- version/wordpress/2.1.2
- version/wordpress/2.1.3
- version/wordpress/2.1.3_rc1
- version/wordpress/2.1.3_rc2
- version/wordpress/2.2
- version/wordpress/2.2.1
- version/wordpress/2.2.2
- version/wordpress/2.2.3
- version/wordpress/2.2_revision5002
- version/wordpress/2.2_revision5003
- version/wordpress/2.3
- version/wordpress/2.3.1