CVE-2006-5858 json
Adobe ColdFusion MX 7 through 7.0.2, and JRun 4, when run on Microsoft IIS, allows remote attackers to read arbitrary files, list directories, or read source code via a double URL-encoded NULL byte in a ColdFusion filename, such as a CFM file.
published 19y ago modified 5mo ago also EUVD-2006-5842
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.6%
- EPSS 13.6% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
Adobe ColdFusion MX 7 through 7.0.2, and JRun 4, when run on Microsoft IIS, allows remote attackers to read arbitrary files, list directories, or read source code via a double URL-encoded NULL byte in a ColdFusion filename, such as a CFM file.
Patch / fix
Is CVE-2006-5858 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
13.60% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
adobe.com
/support/security/bulletins/apsb07-02.html
patch, vendor-advisory
-
securityfocus.com
/archive/1/457799/100/0/threaded
mailing-list, third-party-advisory, vdb-entry
-
secunia.com
/advisories/23668
third-party-advisory
-
labs.idefense.com
/intelligence/vulnerabilities/display.php?id=466
third-party-advisory, broken-link
-
securitytracker.com
/id?1017490
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/21978
vdb-entry, third-party-advisory
-
osvdb.org
/32123
vdb-entry, broken-link
-
vupen.com
/english/advisories/2007/0116
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/31411
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2006-5858
- NVD CVE-2006-5858
Fencer Intel 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.