CVE-2023-26347
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 · uneditedAdobe ColdFusion versions 2023.5 (and earlier) and 2021.11 (and earlier) are affected by an Improper Access Control vulnerability that could result in a Security feature bypass. An unauthenticated attacker could leverage this vulnerability to access the administration CFM and CFC endpoints. Exploitation of this issue does not require user interaction.
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 · high confidenceAdobe ColdFusion versions 2023.5 and earlier, and 2021.11 and earlier contain an improper access control vulnerability that allows unauthenticated attackers to bypass security controls and access administration CFM and CFC endpoints. This represents a security feature bypass with no user interaction required.
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< 2021= 2021= 2023CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ColdFusion versionLocate and read the ColdFusion version file or use the ColdFusion Administrator interface to determine the exact installed version numberAffected if The installed version is 2023.5 or earlier, or 2021.11 or earlier, or any version prior to 2021 update 12
-
Verify access to administration endpointsAttempt to access the ColdFusion Administrator interface (typically at /CFIDE/administrator/) and common admin CFC endpoints without providing credentialsAffected if The administration interface or admin CFC endpoints are accessible without authentication
-
Test for security control bypassSend direct HTTP requests to known administration CFM or CFC endpoints (such as scheduler, settings, or datasources admin endpoints) without including valid authentication credentialsAffected if Requests to admin endpoints succeed without authentication, indicating the security controls can be bypassed
-
Check ColdFusion 2021 build numberIn ColdFusion 2021, check both the update version (should be 12 or later for fixed version) and the underlying build version to confirm full patch statusAffected if The update version is 11 or earlier, or the build indicates a version prior to the December 2023 patch
You are affected if your installed ColdFusion version falls within 2023.5 or earlier, or 2021.11 or earlier, AND the administration endpoints are accessible without authentication due to the security control bypass.
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.
dbcve · scoped2021
Apply vendor-supplied patches by updating ColdFusion to version 2023.6 or later, and 2021.12 or later, to remediate the access control bypass.
ColdFusion 2021 Update 12+ or ColdFusion 2023 Update 6+
- 1. Identify the currently installed ColdFusion version by checking the ColdFusion Administrator or the version file
- 2. For ColdFusion 2021: Upgrade to ColdFusion 2021 Update 12 or later
- 3. For ColdFusion 2023: Upgrade to ColdFusion 2023 Update 6 or later
- 4. Download the appropriate update from the Adobe ColdFusion downloads page (helpx.adobe.com)
- 5. Apply the update following Adobe's standard update installation procedures
- 6. After upgrading, verify that the ColdFusion Administrator is no longer accessible to unauthenticated users
- 7. Test critical application functionality to ensure the update did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26347 — 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-2023-26347 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