dbcve.org
ColdfusionApplication · Adobe

CVE-2025-61809

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
ColdFusion versions 2025.4, 2023.16, 2021.22 and earlier are affected by an Improper Input Validation vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read and write access. Exploitation of this issue does not require user interaction and scope is unchanged.

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 confidence

ColdFusion versions 2025.4, 2023.16, 2021.22 and earlier contain an improper input validation vulnerability that allows attackers to bypass security measures, enabling unauthorized read and write access to system resources. This critical flaw is exploitable without user interaction.

MitigationApply vendor-provided patches for ColdFusion versions 2025.4, 2023.16, 2021.22 and earlier to remediate the improper input validation vulnerability.

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
ColdfusionApplication
Affected:= 2021= 2023= 2025

CVSS 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the ColdFusion installation and identify its version
    Access the ColdFusion Administrator interface (typically at /cfide/administrator/) or the ColdFusion welcome page, and note the exact version number displayed. Alternatively, check the version via command line if available.
    Affected if The displayed version is 2025.4 or lower, 2023.16 or lower, 2021.22 or lower, or any earlier 2021/2023/2025 release.
  2. Confirm the major release year
    Verify that the product is Adobe ColdFusion (not a third-party fork) and identify whether it is the 2021, 2023, or 2025 major release.
    Affected if The major release is 2021, 2023, or 2025.
  3. Compare the full version string against affected ranges
    Extract the complete version string (for example, 2021.18.0.329500) and compare the minor version number against the patched releases: 2021.22, 2023.16, and 2025.4.
    Affected if The installed version falls at or below 2021.22, 2023.16, or 2025.4 within its respective major release line.
  4. Assess network exposure
    Determine whether the ColdFusion server is directly accessible from untrusted networks or the internet, since this flaw is exploitable without user interaction.
    Affected if The ColdFusion ports (default 8500, 8080, or 80/443) are exposed to untrusted network segments.

You are affected if your installed ColdFusion version is 2025.4 or lower, 2023.16 or lower, or 2021.22 or lower, and the server is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for ColdFusion versions 2025.4, 2023.16, 2021.22 and earlier to remediate the improper input validation vulnerability.

Recommended fix High confidence

ColdFusion 2021 Update 23+, ColdFusion 2023 Update 17+, ColdFusion 2025 Update 5+

  1. 1. Identify your current ColdFusion version by checking the ColdFusion Administrator or the version.json file in the cfroot directory
  2. 2. Download the appropriate security update from Adobe's official helpx.adobe.com repository for your ColdFusion edition
  3. 3. For ColdFusion 2021: Apply Update 23 or later (version 2021.23+)
  4. 4. For ColdFusion 2023: Apply Update 17 or later (version 2023.17+)
  5. 5. For ColdFusion 2025: Apply Update 5 or later (version 2025.5+)
  6. 6. Backup your ColdFusion installation and configuration before applying the update
  7. 7. Stop the ColdFusion application server service
  8. 8. Run the installer for the security update
Caveat Adobe patch updates typically include backward-compatible fixes; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coldfusion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61809 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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