CVE-2026-47929
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 2023.19, 2025.8 and earlier are affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current user. A high-privileged attacker could exploit this vulnerability to gain elevated access or control over the victim's account or session. The vulnerable component is restricted to an administrative network zone by default. Exploitation of this issue does not require user interaction. Scope is changed.
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 confidenceColdFusion versions 2023.19, 2025.8 and earlier contain an Incorrect Authorization vulnerability that allows a high-privileged attacker to bypass authorization controls and achieve arbitrary code execution in the context of the current user. The scope change indicates the vulnerability impacts components beyond the originally vulnerable authorization module.
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= 2023= 2025CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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 versionAccess the ColdFusion Administrator console, typically at /cfide/administrator/, or check the version file in the installation directory. Alternatively, query the server for the ColdFusion version via the Administrator API or check the license file.Affected if The installed version is ColdFusion 2023 update 19 or earlier, or ColdFusion 2025 update 8 or earlier.
-
Confirm high-privileged account presenceReview the ColdFusion user directory or Administrator users list to identify accounts with Administrator or elevated privileges. Check for accounts with permissions to access the Administrator console, cfadmin privileges, or roles beyond standard users.Affected if The environment contains one or more high-privileged accounts that could be targeted by an attacker to exploit this authorization bypass.
-
Review authentication and authorization logsExamine ColdFusion logs in the logs directory (typically /cfusion/logs/) for the administrator, server, or application logs. Search for failed authorization attempts, unexpected privilege escalation events, or unauthorized access to restricted endpoints.Affected if Logs show any unauthorized access attempts, authorization bypass patterns, or actions performed by accounts beyond their assigned privileges.
-
Inspect for unexpected code execution patternsReview ColdFusion scheduled tasks, CFCs, CFM templates, and any custom code in the web root for unfamiliar or suspicious code that may indicate prior exploitation. Check the cfusion/lib or webroot directories for newly created or modified files.Affected if There are scheduled tasks, templates, or code files that were not authored by your team, or there are signs of arbitrary code execution having occurred.
An environment is affected if it runs ColdFusion 2023 update 19 or earlier, or ColdFusion 2025 update 8 or earlier, and contains high-privileged accounts that could be leveraged to bypass authorization controls.
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 · scopedApply the vendor-provided patches for ColdFusion 2023 and 2025 versions as soon as they become available. Restrict administrative access to ColdFusion administrator interfaces and implement network segmentation as an interim control.
ColdFusion 2023.20+ or ColdFusion 2025.9+ (depending on your product line)
- 1. Identify the current ColdFusion installation version by checking the ColdFusion Administrator or the version information in the installation directory.
- 2. For ColdFusion 2023: Upgrade to version 2023.20 or later.
- 3. For ColdFusion 2025: Upgrade to version 2025.9 or later.
- 4. After upgrading, verify the ColdFusion services restart successfully.
- 5. Review Adobe's official release notes for the new version to ensure all security patches are applied.
- 6. Test critical applications to confirm normal functionality after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47929 — 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-2026-47929 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