ColdfusionApplication · Adobe

CVE-2019-8072

HIGH · 7.5 CVSS v3.1 Published 2019-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
ColdFusion 2018- update 4 and earlier and ColdFusion 2016- update 11 and earlier have a Security bypass vulnerability. Successful exploitation could lead to Information Disclosure in the context of the current user.

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

ColdFusion 2018 (update 4 and earlier) and ColdFusion 2016 (update 11 and earlier) contain a security bypass vulnerability that allows an attacker to bypass existing security controls and disclose information accessible to the current user context.

MitigationApply the appropriate ColdFusion security updates (update 5 for 2018, update 12 for 2016) or later from Adobe to address this vulnerability.

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:= 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 product version
    Access the ColdFusion Administrator console (typically at /CFIDE/administrator/) and navigate to the System Information or Settings page to view the installed version number. Alternatively, check the version file in the ColdFusion installation directory or run 'cfadmin' related diagnostics.
    Affected if The installed version is ColdFusion 2016 or ColdFusion 2018
  2. Determine installed update level
    In the ColdFusion Administrator, locate the update version or hot fix level displayed in the System Information section. This shows which specific update (e.g., Update 4, Update 11) is currently applied.
    Affected if For ColdFusion 2018, the installed update is Update 4 or earlier. For ColdFusion 2016, the installed update is Update 11 or earlier
  3. Verify ColdFusion is accessible to untrusted users
    Confirm whether the ColdFusion instance is exposed to the network or accessible to users outside the trusted internal environment. Check network listeners and firewall rules for ports 8500 (default) or 443 (if using web server connector).
    Affected if The ColdFusion Administrator or its web services are reachable by untrusted or anonymous users
  4. Check for existence of sensitive data or endpoints
    Review whether the ColdFusion application handles sensitive information or exposes web services, APIs, or file endpoints that could be targeted for information disclosure.
    Affected if The application contains sensitive data, user-specific content, or restricted endpoints accessible through ColdFusion web services

The environment is affected if ColdFusion 2018 with Update 4 or earlier, or ColdFusion 2016 with Update 11 or earlier, is installed and the instance is accessible to untrusted users who could exploit the security bypass to access information within their current user context.

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 ColdFusion security updates (update 5 for 2018, update 12 for 2016) or later from Adobe to address this vulnerability.

Fix this in Coldfusion Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8072 — 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-2019-8072 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