CVE-2025-61822
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 2025.4, 2023.16, 2021.22 and earlier are affected by an Improper Input Validation vulnerability that could lead to arbitrary file system write. An attacker could exploit this vulnerability to write malicious files to arbitrary locations on the file system. Exploitation of this issue does not require user interaction and 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 · high confidenceColdFusion versions 2025.4, 2023.16, 2021.22 and earlier contain an improper input validation vulnerability that allows authenticated or unauthenticated attackers to write arbitrary files to the file system. The lack of proper validation on file write operations enables path traversal and arbitrary file creation without user interaction. The scope change indicates the vulnerability impacts components beyond the vulnerable service itself.
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= 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:H/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 installation and versionCheck the version.json file in the ColdFusion installation directory (typically at [cf_install_root]/cfusion/lib/version.json) or access the ColdFusion Administrator dashboard and view the About ColdFusion pageAffected if The installed version is 2021.22 or earlier, 2023.16 or earlier, or 2025.4 or earlier
-
Confirm ColdFusion is accessible over networkVerify if the ColdFusion web server connector is bound to external network interfaces (0.0.0.0) or check the server's firewall rules for inbound access to ColdFusion ports (typically 8500, 8443, or standard HTTP/HTTPS ports)Affected if ColdFusion is directly accessible from untrusted networks without authentication protection
-
Review web server access logs for file write attemptsExamine ColdFusion runtime logs (in [cf_install_root]/cfusion/logs) and web server logs for suspicious requests containing path traversal patterns such as '../', '..\', or absolute paths in file upload/download parametersAffected if Log entries show file operation requests with unusual path sequences or attempts to write files outside expected directories
-
Inspect for unexpected files in web rootScan the web root directory (typically [cf_install_root]/cfusion/wwwroot) and any mapped virtual directories for newly created or modified files, especially executable scripts (cfm, cfc, asp, php, jsp), config files, or system utilities that were not intentionally deployedAffected if Unexpected script files or config changes are found in directories outside the normal application scope
-
Check for unauthorized CFIDE modificationsReview the cfide directory (ColdFusion IDE components) and its subdirectories for new or modified cfm files, especially in locations like cfide/administrator/, cfide/debug/, or cfide/scripts/Affected if New or modified files exist in cfide directories that were not part of the original installation
A system is affected if it runs any version of ColdFusion 2021 through 2021.21, 2023 through 2023.15, or 2025 through 2025.3, and the file write functionality is exposed to network or local attackers.
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 · scopedUpgrade to the latest ColdFusion version that includes the patch for this vulnerability, as indicated by the fixed version releases in the affected version strings.
ColdFusion 2021 Update 23+, ColdFusion 2023 Update 17+, or ColdFusion 2025 Update 5+
- Identify your current ColdFusion installation version (2021, 2023, or 2025)
- Navigate to the Adobe ColdFusion downloads page at helpx.adobe.com
- Download the latest available update for your installed version: ColdFusion 2021 Update 23 or later, ColdFusion 2023 Update 17 or later, or ColdFusion 2025 Update 5 or later
- Before applying the update, perform a full backup of your ColdFusion instance including the lib directory, configuration files, and any custom code
- Stop the ColdFusion application server service
- Apply the downloaded update installer following Adobe's standard update installation procedure
- Restart the ColdFusion application server service
- Verify the update was successful by checking the ColdFusion Administrator > System Information page shows the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61822 — 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-2025-61822 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