CVE-2007-6318

MEDIUMCVSS v2 · 6.86.8
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.8 — NVD rates that MEDIUM (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:M/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 9.2% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized
6.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 9.2%CVSS v2: 6.8Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

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.

CVSS v2.0 (legacy)
6.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.8MEDIUMlow confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
The EG Score, 6.8 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
9.2%
EPSS %ILE
95th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track or Track* at medium and Track* or Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

December 12, 2007

Last Modified

April 23, 2026

References (12)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress—
  • every version up to 2.3.2-1: fixed in 2.3.2-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress—
  • every version up to 2.3.2-1: fixed in 2.3.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress—
  • every version up to 2.3.2-1: fixed in 2.3.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress—
  • every version up to 2.3.2-1: fixed in 2.3.2-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 17× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 80 of 106 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 20 repeat rows among the latest 100 are merged into the row they repeat. The 26 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:37 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  2. 2026-10-10 19:53 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  3. 2026-10-09 20:00 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  4. 2026-10-08 16:33 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  5. 2026-10-07 23:37 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  6. 2026-10-06 15:09 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  7. 2026-10-05 17:37 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  8. 2026-10-04 07:34 UTCOSV refresh
  9. 2026-10-03 14:20 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  10. 2026-10-01 19:42 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  11. 2026-09-30 14:57 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  12. 2026-09-29 07:45 UTCEG score recompute
  13. 2026-09-18 19:20 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  14. 2026-09-17 19:20 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  15. 2026-09-15 03:04 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  16. 2026-09-14 21:44 UTCOSV refresh
  17. 2026-09-12 14:54 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  18. 2026-09-05 15:22 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  19. 2026-09-04 13:55 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  20. 2026-09-04 04:59 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  21. 2026-08-30 01:14 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  22. 2026-08-26 21:16 UTCOSV refresh
  23. 2026-08-10 11:39 UTCOSV refresh
  24. 2026-08-08 16:30 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  25. 2026-08-07 16:20 UTCEPSS rescoreEPSS 9.2% · 94th percentile
Show 55 more
  1. 2026-08-06 13:41 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  2. 2026-08-05 19:11 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  3. 2026-08-04 15:03 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  4. 2026-08-03 10:28 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  5. 2026-07-30 16:22 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  6. 2026-07-30 01:25 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  7. 2026-07-28 15:30 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  8. 2026-07-26 13:34 UTCEG score recomputeFirst assessed: 6.8 MEDIUM
  9. 2026-07-25 14:12 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  10. 2026-07-25 12:11 UTCOSV refresh
  11. 2026-07-24 14:11 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  12. 2026-07-23 14:13 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  13. 2026-07-23 00:55 UTCEG score recompute
  14. 2026-07-23 00:33 UTCEG score recompute
  15. 2026-07-22 23:59 UTCEG score recompute
  16. 2026-07-22 21:38 UTCEG score recompute
  17. 2026-07-22 14:03 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  18. 2026-07-21 15:19 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  19. 2026-07-20 17:03 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  20. 2026-07-18 09:59 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  21. 2026-07-16 16:58 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  22. 2026-07-15 16:54 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  23. 2026-07-15 01:55 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  24. 2026-07-11 08:22 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  25. 2026-07-08 15:09 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  26. 2026-07-08 06:57 UTCOSV refresh
  27. 2026-07-06 16:22 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  28. 2026-07-05 02:26 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  29. 2026-07-04 06:27 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  30. 2026-07-02 14:00 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  31. 2026-07-01 15:02 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  32. 2026-06-30 23:19 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  33. 2026-06-29 14:02 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  34. 2026-06-28 04:52 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  35. 2026-06-27 03:04 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  36. 2026-06-25 13:46 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  37. 2026-06-24 14:02 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  38. 2026-06-23 21:29 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  39. 2026-06-19 18:55 UTCOSV refresh
  40. 2026-06-18 17:49 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  41. 2026-06-17 17:49 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  42. 2026-06-16 17:49 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  43. 2026-06-15 17:44 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  44. 2026-06-13 22:57 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  45. 2026-06-12 23:08 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  46. 2026-06-10 22:14 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  47. 2026-06-10 13:17 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  48. 2026-06-08 14:13 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  49. 2026-06-06 13:44 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  50. 2026-06-05 22:44 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  51. 2026-06-05 06:07 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  52. 2026-06-04 13:09 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  53. 2026-06-02 20:10 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  54. 2026-06-01 13:49 UTCEPSS rescoreEPSS 3.5% · 87th percentile
  55. 2026-05-31 22:28 UTCEPSS rescoreEPSS 3.5% · 87th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-4721✓ verified
    Published Dec 11, 2007

    WordPress Core 2.3.1 - Charset SQL Injection

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2007-6318?
CVE-2007-6318 is a medium-severity vulnerability; its CVE record was published on December 12, 2007. 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.
When was CVE-2007-6318 made public?
CVE-2007-6318 was made public on December 10, 2007: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on December 12, 2007. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2007-6318 actively exploited?
CVE-2007-6318 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 9.2% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-6318?
A fix for CVE-2007-6318 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2007-6318

Explore →

Is Your Infrastructure Affected by CVE-2007-6318?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs