CVE-2019-7092
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 · uneditedColdFusion versions Update 1 and earlier, Update 7 and earlier, and Update 15 and earlier have a cross site scripting 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 confidenceAdobe ColdFusion versions Update 1 and earlier (release train 1), Update 7 and earlier (release train 7), and Update 15 and earlier (release train 15) contain a reflected cross-site scripting (XSS) vulnerability. Attackers can inject malicious scripts through vulnerable parameters, potentially stealing session cookies or other sensitive information from users.
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= 11.0= 2016= 2018CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ColdFusion product versionAccess the ColdFusion Administrator console (usually at /cfide/administrator/ or /ColdFusion2016/administrator/ for 2016) and check the version displayed on the login or about page. Alternatively, check the version.ini or the cfadmin for the installed version.Affected if The installed version is ColdFusion 11.0, ColdFusion 2016, or ColdFusion 2018 with update level at or below Update 1, Update 7, or Update 15 respectively.
-
Determine ColdFusion update/hotfix levelIn ColdFusion Administrator, navigate to the Updates section to view installed updates. Alternatively, check the file lib/coldfusionVersion.properties in the installation directory for the AppliedHotfixes or UpdateLevel value.Affected if The AppliedHotfixes or UpdateLevel value is missing, blank, or shows Update 1 or earlier for CF11, Update 7 or earlier for CF2016, or Update 15 or earlier for CF2018.
-
Verify ColdFusion administrator accessConfirm that the ColdFusion Administrator interface is accessible (even if password-protected). The XSS vulnerability exists in parameters passed through web requests.Affected if ColdFusion Administrator or any ColdFusion web application is reachable and processing user-supplied parameters.
Your environment is affected if you are running ColdFusion 11.0, 2016, or 2018 and the installed update level is at or below the thresholds specified (Update 1, 7, or 15 respectively).
Generated from the published advisory. Verify against your own configuration.
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 dataApply the appropriate ColdFusion update/hotfix from Adobe to address the XSS vulnerability. Implement output encoding and input validation as defense-in-depth measures for user-supplied data.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7092 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7092 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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