ColdfusionApplication · Adobe

CVE-2018-15962

MEDIUM · 5.3 CVSS v3.1 Published 2018-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe ColdFusion versions July 12 release (2018.0.0.310739), Update 6 and earlier, and Update 14 and earlier have a directory listing vulnerability. Successful exploitation could lead to information disclosure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Adobe ColdFusion versions July 12 release (2018.0.0.310739), Update 6 and earlier for certain branches, and Update 14 and earlier have a directory listing vulnerability. This allows remote attackers to obtain directory listings by accessing certain URLs, potentially exposing sensitive file paths, configuration files, and other resources that should not be publicly accessible.

MitigationApply the appropriate Adobe ColdFusion security patch for this vulnerability, or disable directory browsing in the web server/ColdFusion configuration to prevent unauthenticated directory listing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ColdfusionApplication
Affected:= 11.0= 2016= 2018

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ColdFusion version
    Check the ColdFusion administrator console or registry for the exact version and update level installed. Look for version indicators such as 11.0, 2016, or 2018 and note the specific update version applied.
    Affected if The installed version is ColdFusion 11.0, ColdFusion 2016, or ColdFusion 2018 with an update level at or below the July 12 release (2018.0.0.310739), Update 6 for 11.x, or Update 14 for 2016/2018.
  2. Verify web server directory listing config
    Review the web server configuration (IIS httpd.conf, Apache conf, or equivalent) and ColdFusion server configuration for directory browsing or auto indexing settings.
    Affected if Directory listing is enabled at the web server or ColdFusion level, allowing unauthenticated access to directory contents.
  3. Test for vulnerable URL endpoints
    Attempt to access known directory listing endpoints on the ColdFusion server. These typically include URLs with patterns such as /CFIDE/administrator/ or other ColdFusion administrative paths that may expose directory indexes.
    Affected if Requesting specific URLs returns directory listings showing file structures rather than access denied or proper file handling.
  4. Inspect exposed configuration files
    Check whether configuration files such as web.xml, neo-*.xml, or other ColdFusion configuration files are accessible via web requests to the affected URLs.
    Affected if Sensitive configuration files or path information is returned in directory listing responses.

A ColdFusion 11.0, 2016, or 2018 installation at or below the specified update levels with directory browsing enabled and accessible vulnerable URL patterns is affected by this directory listing vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate Adobe ColdFusion security patch for this vulnerability, or disable directory browsing in the web server/ColdFusion configuration to prevent unauthenticated directory listing.

Fix this in Coldfusion Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15962 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data