CVE-2016-1113
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 · uneditedCross-site scripting (XSS) vulnerability in Adobe ColdFusion 10 before Update 19, 11 before Update 8, and 2016 before Update 1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceCross-site scripting (XSS) vulnerability in Adobe ColdFusion allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. The vulnerability affects ColdFusion 10 (before Update 19), 11 (before Update 8), and 2016 (before Update 1). This is a standard web-based XSS flaw that could allow session hijacking or defacement.
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= 10.0= 11.0= 2016CVSS 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.1/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 the installed ColdFusion versionAccess the ColdFusion Administrator console or check the version information file. Typically, the version is displayed on the login page or in the Server Settings section of the Administrator.Affected if The installed version is ColdFusion 10, 11, or 2016 (any build)
-
Determine the installed update or hotfix levelCheck the ColdFusion Administrator under the Updates section, or examine the hotfix log or configuration file that tracks applied updates. This will show whether Update 19 (for ColdFusion 10), Update 8 (for ColdFusion 11), or Update 1 (for ColdFusion 2016) has been applied.Affected if The installed update level is below the specified threshold for your version (before Update 19 for CF10, before Update 8 for CF11, or before Update 1 for CF2016)
-
Confirm the web-based administrator interface is accessibleVerify that the ColdFusion Administrator web interface (usually at /CFIDE/administrator/) is accessible over the network. The XSS vulnerability is web-based, so the attack vector requires the admin interface to be reachable.Affected if The ColdFusion Administrator interface is accessible from network locations where untrusted users could inject malicious scripts
A user is affected if they are running ColdFusion 10 before Update 19, ColdFusion 11 before Update 8, or ColdFusion 2016 before Update 1, AND the web administrator interface is accessible.
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 vendor-supplied updates: ColdFusion 10 Update 19, ColdFusion 11 Update 8, or ColdFusion 2016 Update 1. Verify the patch in a staging environment before production deployment.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1113 — 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-2016-1113 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