CVE-2007-6203

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:N/I:P/A:N. 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 80.7% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
4.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 12 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 81%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 81%CVSS v2: 4.3Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 12

A fix is available — apply it.

Apache HTTP Server 2.0.x and 2.2.x does not sanitize the HTTP Method specifier header from an HTTP request when it is reflected back in a "413 Request Entity Too Large" error message, which might allow cross-site scripting (XSS) style attacks using web client components that can send arbitrary headers in requests, as demonstrated via an HTTP request containing an invalid Content-length value, a similar issue to CVE-2006-3918.

Live · internet exposure

12 internet-exposed hosts are running an affected version of CVE-2007-6203 right now.

across 8 countries (United States, Japan, France, Hong Kong, Canada)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v2.0 (legacy)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3(low)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

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
Severity43% × 45%
Exploitation81% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
81%
EPSS %ILE
100%
KEV
Not listed

Published

December 3, 2007

Last Modified

April 23, 2026

References (62)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-mpm-perchild (2.2.8-1ubuntu0.5) @ hardy2026-05-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.6-3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.6-3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.6-3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.6-3—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 1× in last 7d / 6× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:20 UTCEPSS rescore
  2. 2026-09-15 03:04 UTCEPSS rescore
  3. 2026-09-14 22:14 UTCOSV refresh
  4. 2026-09-05 15:22 UTCEPSS rescore
  5. 2026-08-30 01:14 UTCEPSS rescore
  6. 2026-08-26 21:33 UTCOSV refresh
  7. 2026-08-10 11:40 UTCOSV refresh
  8. 2026-07-26 13:34 UTCEG score recompute▲ 4.30
  9. 2026-07-25 14:12 UTCEPSS rescore
  10. 2026-07-25 12:11 UTCOSV refresh
  11. 2026-07-24 14:11 UTCEPSS rescore
  12. 2026-07-23 14:13 UTCEPSS rescore
  13. 2026-07-23 00:55 UTCEG score recompute
  14. 2026-07-23 00:33 UTCEG score recompute▼ 8.30
  15. 2026-07-22 23:59 UTCEG score recompute▲ 8.30
  16. 2026-07-22 21:38 UTCEG score recompute
  17. 2026-07-22 14:03 UTCEPSS rescore
  18. 2026-07-21 15:19 UTCEPSS rescore
  19. 2026-07-15 16:54 UTCEPSS rescore
  20. 2026-07-15 16:54 UTCEPSS rescore
  21. 2026-07-08 07:05 UTCOSV refresh
  22. 2026-07-04 06:27 UTCEPSS rescore
  23. 2026-07-04 06:27 UTCEPSS rescore
  24. 2026-07-01 15:02 UTCEPSS rescore
  25. 2026-07-01 15:02 UTCEPSS rescore
Show 49 more
  1. 2026-06-30 23:19 UTCEPSS rescore
  2. 2026-06-30 23:19 UTCEPSS rescore
  3. 2026-06-25 13:46 UTCEPSS rescore
  4. 2026-06-25 13:46 UTCEPSS rescore
  5. 2026-06-23 21:29 UTCEPSS rescore
  6. 2026-06-23 21:29 UTCEPSS rescore
  7. 2026-06-21 01:56 UTCEPSS rescore
  8. 2026-06-21 01:56 UTCEPSS rescore
  9. 2026-06-19 18:55 UTCOSV refresh
  10. 2026-06-18 17:49 UTCEPSS rescore
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-16 17:49 UTCEPSS rescore
  13. 2026-06-16 17:49 UTCEPSS rescore
  14. 2026-06-16 17:49 UTCEPSS rescore
  15. 2026-06-15 17:44 UTCEPSS rescore
  16. 2026-06-13 22:57 UTCEPSS rescore
  17. 2026-06-12 23:08 UTCEPSS rescore
  18. 2026-06-10 22:14 UTCEPSS rescore
  19. 2026-06-10 13:17 UTCEPSS rescore
  20. 2026-06-08 14:13 UTCEPSS rescore
  21. 2026-06-07 15:21 UTCEPSS rescore
  22. 2026-06-06 13:44 UTCEPSS rescore
  23. 2026-06-06 13:44 UTCEPSS rescore
  24. 2026-06-05 22:44 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
  26. 2026-06-05 06:07 UTCEPSS rescore
  27. 2026-06-02 20:10 UTCEPSS rescore
  28. 2026-06-02 20:10 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-06-01 13:49 UTCEPSS rescore
  31. 2026-06-01 13:49 UTCEPSS rescore
  32. 2026-05-31 00:13 UTCEPSS rescore
  33. 2026-05-31 00:13 UTCEPSS rescore
  34. 2026-05-30 23:55 UTCEG score recompute
  35. 2026-05-30 23:55 UTCVendor advisory
  36. 2026-05-30 23:55 UTCGHSA enrichment
  37. 2026-05-29 13:40 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-28 13:42 UTCEPSS rescore
  41. 2026-05-24 16:42 UTCEPSS rescore
  42. 2026-05-24 14:51 UTCOSV refresh
  43. 2026-05-21 22:38 UTCEPSS rescore
  44. 2026-05-20 22:36 UTCEPSS rescore
  45. 2026-05-20 22:36 UTCEPSS rescore
  46. 2026-05-20 11:20 UTCEPSS rescore
  47. 2026-05-20 11:20 UTCEPSS rescore
  48. 2026-05-18 21:29 UTCEPSS rescore
  49. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-30835✓ verified
    First seen Nov 30, 2007

    Apache 2.2.4 - 413 Error HTTP Request Method Cross-Site Scripting

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2007-6203?
CVE-2007-6203 is a medium vulnerability published on December 3, 2007. Apache HTTP Server 2.0.x and 2.2.x does not sanitize the HTTP Method specifier header from an HTTP request when it is reflected back in a "413 Request Entity Too Large" error message, which might allow cross-site scripting (XSS) style attacks using web client components that can send arbitrary…
When was CVE-2007-6203 disclosed?
CVE-2007-6203 was first published in the National Vulnerability Database on December 3, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-6203 actively exploited?
CVE-2007-6203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 81% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
How do I remediate CVE-2007-6203?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2007-6203, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2007-6203?

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

Book a Demo →Browse All CVEs