CVE-2003-1409

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 3%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

TOPo 1.43 allows remote attackers to obtain sensitive information by sending an HTTP request with an invalid parameter to (1) in.php or (2) out.php, which reveals the path to the TOPo directory in the error message.

CVSS v3
—
EG Score
0.0(none)
EPSS
82.9%
KEV
Not listed

Published

December 31, 2003

Last Modified

June 16, 2026

References (8)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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-07-13 06:07 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-11 08:22 UTCEPSS rescore
  4. 2026-07-08 15:09 UTCEPSS rescore
  5. 2026-07-04 06:26 UTCEPSS rescore
  6. 2026-07-02 14:00 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-28 14:02 UTCEPSS rescore
  10. 2026-06-28 04:52 UTCEPSS rescore
  11. 2026-06-27 03:04 UTCEPSS rescore
  12. 2026-06-23 21:29 UTCEPSS rescore
  13. 2026-06-22 14:22 UTCEPSS rescore
  14. 2026-06-21 14:52 UTCEPSS rescore
  15. 2026-06-21 01:56 UTCEPSS rescore
  16. 2026-06-19 19:22 UTCEPSS rescore
  17. 2026-06-19 19:22 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-15 17:43 UTCEPSS rescore
  25. 2026-06-13 22:56 UTCEPSS rescore
Show 38 more
  1. 2026-06-12 23:08 UTCEPSS rescore
  2. 2026-06-11 13:55 UTCEPSS rescore
  3. 2026-06-10 22:13 UTCEPSS rescore
  4. 2026-06-10 13:17 UTCEPSS rescore
  5. 2026-06-08 14:13 UTCEPSS rescore
  6. 2026-06-07 15:21 UTCEPSS rescore
  7. 2026-06-06 13:44 UTCEPSS rescore
  8. 2026-06-06 13:44 UTCEPSS rescore
  9. 2026-06-06 13:44 UTCEPSS rescore
  10. 2026-06-05 22:43 UTCEPSS rescore
  11. 2026-06-05 22:43 UTCEPSS rescore
  12. 2026-06-05 06:07 UTCEPSS rescore
  13. 2026-06-04 13:09 UTCEPSS rescore
  14. 2026-06-02 20:10 UTCEPSS rescore
  15. 2026-06-01 13:49 UTCEPSS rescore
  16. 2026-06-01 13:49 UTCEPSS rescore
  17. 2026-05-31 22:28 UTCEPSS rescore
  18. 2026-05-31 16:42 UTCEG score recompute
  19. 2026-05-31 16:42 UTCGHSA enrichment
  20. 2026-05-31 00:13 UTCEPSS rescore
  21. 2026-05-31 00:13 UTCEPSS rescore
  22. 2026-05-29 13:40 UTCEPSS rescore
  23. 2026-05-29 13:40 UTCEPSS rescore
  24. 2026-05-28 13:42 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-27 13:37 UTCEPSS rescore
  28. 2026-05-26 13:41 UTCEPSS rescore
  29. 2026-05-26 13:41 UTCEPSS rescore
  30. 2026-05-26 07:16 UTCEPSS rescore
  31. 2026-05-26 07:16 UTCEPSS rescore
  32. 2026-05-24 16:42 UTCEPSS rescore
  33. 2026-05-22 21:15 UTCEPSS rescore
  34. 2026-05-20 22:36 UTCEPSS rescore
  35. 2026-05-20 11:20 UTCEPSS rescore
  36. 2026-05-20 11:20 UTCEPSS rescore
  37. 2026-05-18 21:29 UTCEPSS rescore
  38. 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-22222✓ verified
    First seen Feb 4, 2003

    TOPO 1.41 - Full Path Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2003-1409?
CVE-2003-1409 is a none vulnerability published on December 31, 2003. TOPo 1.43 allows remote attackers to obtain sensitive information by sending an HTTP request with an invalid parameter to (1) in.php or (2) out.php, which reveals the path to the TOPo directory in the error message.
When was CVE-2003-1409 disclosed?
CVE-2003-1409 was first published in the National Vulnerability Database on December 31, 2003, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2003-1409 actively exploited?
CVE-2003-1409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2003-1409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-1409, 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

Explore the affected products and dependency analysis for CVE-2003-1409

Explore →

Is Your Infrastructure Affected by CVE-2003-1409?

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

Start Free Scan →Browse All CVEs