Skip to content
Fencer Vulns
medium 6.8

CVE-2007-6318 json

SQL injection vulnerability in wp-includes/query.php in WordPress 2.3.1 and earlier allows remote attackers to execute arbitrary SQL comman…

published 2007-12-12 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6285

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.2%
EPSS 9.2% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • wordpress Debian 14, Debian 13, Debian 12 2.3.2-1

debian advisories DEBIAN-CVE-2007-6318

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2007-6318 updated

wordpress: SQL injection when certain DB charsets are used

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-4721)
  2. Published

Exploit prediction

9.16% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-4721 WordPress Core 2.3.1 - Charset SQL Injection webapps, 2007-12-11
  • abelcheung.org http://www.abelcheung.org/advisory/20071210-wordpress-charset.txt referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/26795 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.