CVE-2007-6388

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 75.9% 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
Elevated
4.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 20 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 76%
CISA-KEV: Not listedEPSS PROB: 76%CVSS v2: 4.3Exploit: Elevated riskExposed: 20

A fix is available — apply it.

Cross-site scripting (XSS) vulnerability in mod_status in the Apache HTTP Server 2.2.0 through 2.2.6, 2.0.35 through 2.0.61, and 1.3.2 through 1.3.39, when the server-status page is enabled, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Live · internet exposure

20 internet-exposed hosts are running an affected version of CVE-2007-6388 right now.

across 11 countries (United States, Japan, Germany, Korea, Republic of, Australia)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
54(Track)
EG Risk 54/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%
Exploitation76% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
76%
EPSS %ILE
99%
KEV
Not listed

Published

January 8, 2008

Last Modified

April 23, 2026

References (188)

Vendor Advisories for CVE-2007-6388(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-mpm-perchild (2.2.4-3ubuntu0.1) @ gutsy2026-05-30ubuntu
redhatxml-commons-0:1.3.02-2jpp_1rh2010-08-04redhat
redhatrhn-modperl-0:1.29-16.rhel42008-06-30redhat
redhattomcat5-0:5.0.30-0jpp_10rh2008-06-30redhat
redhathttpd-0:2.2.3-11.el5_1.32008-01-15redhat
redhathttpd-0:2.0.46-70.ent2008-01-15redhat
redhathttpd-0:2.0.59-1.el4s1.102008-01-15redhat
redhathttpd-0:2.0.52-38.ent.22008-01-15redhat
redhatapache-0:1.3.27-14.ent2008-01-15redhat

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.8-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.8-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.8-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.8-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 0× in last 7d / 4× 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-08-10 11:09 UTCOSV refresh
  2. 2026-08-07 16:20 UTCEPSS rescore
  3. 2026-08-04 15:03 UTCEPSS rescore
  4. 2026-07-30 16:22 UTCEPSS rescore
  5. 2026-07-26 13:34 UTCEG score recompute▲ 4.30
  6. 2026-07-25 14:12 UTCEPSS rescore
  7. 2026-07-25 11:41 UTCOSV refresh
  8. 2026-07-24 14:11 UTCEPSS rescore
  9. 2026-07-23 00:55 UTCEG score recompute
  10. 2026-07-23 00:33 UTCEG score recompute▼ 7.50
  11. 2026-07-22 23:59 UTCEG score recompute▲ 7.50
  12. 2026-07-22 21:38 UTCEG score recompute
  13. 2026-07-22 14:03 UTCEPSS rescore
  14. 2026-07-21 15:19 UTCEPSS rescore
  15. 2026-07-20 17:03 UTCEPSS rescore
  16. 2026-07-15 16:54 UTCEPSS rescore
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-13 06:07 UTCEPSS rescore
  19. 2026-07-08 06:27 UTCOSV refresh
  20. 2026-07-04 06:27 UTCEPSS rescore
  21. 2026-07-04 06:27 UTCEPSS rescore
  22. 2026-07-01 15:02 UTCEPSS rescore
  23. 2026-07-01 15:02 UTCEPSS rescore
  24. 2026-06-30 23:19 UTCEPSS rescore
  25. 2026-06-30 23:19 UTCEPSS rescore
Show 45 more
  1. 2026-06-28 14:03 UTCEPSS rescore
  2. 2026-06-28 04:52 UTCEPSS rescore
  3. 2026-06-27 03:04 UTCEPSS rescore
  4. 2026-06-25 13:46 UTCEPSS rescore
  5. 2026-06-25 13:46 UTCEPSS rescore
  6. 2026-06-23 21:29 UTCEPSS rescore
  7. 2026-06-23 21:29 UTCEPSS rescore
  8. 2026-06-22 14:22 UTCEPSS rescore
  9. 2026-06-21 14:53 UTCEPSS rescore
  10. 2026-06-21 01:56 UTCEPSS rescore
  11. 2026-06-21 01:56 UTCEPSS rescore
  12. 2026-06-19 18:25 UTCOSV refresh
  13. 2026-06-17 17:49 UTCEPSS rescore
  14. 2026-06-17 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-05 22:44 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-04 13:09 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-06-02 20:10 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 22:28 UTCEPSS rescore
  29. 2026-05-30 23:30 UTCEG score recompute
  30. 2026-05-30 23:30 UTCVendor advisory
  31. 2026-05-30 23:30 UTCGHSA enrichment
  32. 2026-05-28 13:42 UTCEPSS rescore
  33. 2026-05-28 13:42 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-27 13:38 UTCEPSS rescore
  36. 2026-05-27 13:37 UTCEPSS rescore
  37. 2026-05-27 13:37 UTCEPSS rescore
  38. 2026-05-24 16:42 UTCEPSS rescore
  39. 2026-05-22 21:15 UTCEPSS rescore
  40. 2026-05-22 21:15 UTCEPSS rescore
  41. 2026-05-22 17:43 UTCOSV refresh
  42. 2026-05-20 22:36 UTCEPSS rescore
  43. 2026-05-20 22:36 UTCEPSS rescore
  44. 2026-05-18 21:29 UTCEPSS rescore
  45. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2007-6388?
CVE-2007-6388 is a medium vulnerability published on January 8, 2008. Cross-site scripting (XSS) vulnerability in mod_status in the Apache HTTP Server 2.2.0 through 2.2.6, 2.0.35 through 2.0.61, and 1.3.2 through 1.3.39, when the server-status page is enabled, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
When was CVE-2007-6388 disclosed?
CVE-2007-6388 was first published in the National Vulnerability Database on January 8, 2008, 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-6388 actively exploited?
CVE-2007-6388 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 76% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
How do I remediate CVE-2007-6388?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2007-6388, 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-6388

Explore →

Is Your Infrastructure Affected by CVE-2007-6388?

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

Start Free Scan →Browse All CVEs