CVE-2026-47932
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 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. The vulnerable component is restricted to an administrative network zone by default. Exploitation of this issue requires user interaction in that a victim must open a malicious file. 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 a path traversal vulnerability that allows attackers to escape restricted directories and execute arbitrary code in the context of the current user by tricking a victim into opening a malicious file.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 or check the version file (usually in /CFIDE/adminapi or via the 'server.coldfusion.productversion' system property). On Windows, also check the installer info in Add/Remove Programs.Affected if The installed version is 2023.19 or earlier, or 2025.8 or earlier, or falls within the = 2023 or = 2025 version families at vulnerable patch levels.
-
Determine if file upload or file processing features are enabledReview ColdFusion Administrator settings under 'Server Settings' or 'File Upload' configurations. Check for enabled handlers for file types that could contain malicious path traversal sequences.Affected if File upload, file serving, or any feature that processes user-supplied file paths is enabled and accessible to users.
-
Inspect custom tag and CFM file directories for path traversal hooksSearch the web root and /CFIDE directories for CFM files that accept file path parameters (look for 'file', 'path', 'filename', 'directory' in URL parameters or form fields). Review any custom file viewer or download handlers.Affected if Custom or built-in ColdFusion files that handle file path parameters are present and accessible without additional authentication.
-
Review web server connector configurationCheck the web server connector (IIS, Apache) configuration for ColdFusion to identify any URL patterns that may allow path traversal sequences like '../' in request URIs.Affected if The web server allows URL-encoded or decoded path traversal sequences to reach ColdFusion request handlers.
A system is affected if it runs Adobe ColdFusion 2023 (up to 2023.19) or 2025 (up to 2025.8) with any file handling or path-processing functionality accessible to users.
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 patch immediately, maintain network segmentation keeping ColdFusion in administrative zones, and train users to avoid opening untrusted files.
ColdFusion 2023 version 2023.20 or later; ColdFusion 2025 version 2025.9 or later
- Upgrade ColdFusion 2023 to version 2023.20 or later by following the Adobe upgrade documentation
- Upgrade ColdFusion 2025 to version 2025.9 or later by following the Adobe upgrade documentation
- After upgrading, verify the patch was applied correctly by checking the ColdFusion administrator about box or version information
- Test that the path traversal vulnerability is no longer exploitable in your environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47932 — 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-47932 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