dbcve.org
ColdfusionApplication · Adobe

CVE-2025-64897

MEDIUM · 5.6 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 →
56/100
Remediation priority · Elevated

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 Access Control vulnerability. A low privileged attacker could leverage this vulnerability to bypass security measures and gain limited unauthorized write access potentially resulting in denial of service. Exploitation of this issue requires 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 · moderate confidence

This is an Improper Access Control vulnerability in ColdFusion versions 2025.4, 2023.22, 2021.22 and earlier. A low-privileged attacker can bypass security measures to gain limited unauthorized write access, potentially leading to denial of service. The exploit requires user interaction, suggesting social engineering or tricking an authenticated user into performing certain actions.

MitigationApply the latest Adobe ColdFusion security patches for versions 2025.4, 2023.22, and 2021.22. Review and enforce least-privilege access controls while awaiting the patch, and educate users about social engineering risks given the user interaction requirement.

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

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

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

  1. Identify installed ColdFusion version
    Check the ColdFusion administrator interface (typically at /cfide/administrator/) or run the command: cfconfig show or check the version file in the ColdFusion installation directory
    Affected if The version displayed is 2021.x, 2023.x, or 2025.x (specifically any version at or before 2021.22, 2023.22, or 2025.4)
  2. Confirm version is within vulnerable range
    Compare your exact installed version number against the affected list: 2021.22 and earlier, 2023.22 and earlier, 2025.4 and earlier. Note that the specific fixed versions are 2025.4, 2023.22, 2021.22 - versions at or below these points are vulnerable.
    Affected if Your ColdFusion version is at or below any of these thresholds: 2025.4, 2023.22, or 2021.22

If your ColdFusion installation shows a version at or below 2025.4, 2023.22, or 2021.22, you are running a vulnerable version and should apply the latest security patches.

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 the latest Adobe ColdFusion security patches for versions 2025.4, 2023.22, and 2021.22. Review and enforce least-privilege access controls while awaiting the patch, and educate users about social engineering risks given the user interaction requirement.

Recommended fix Moderate confidence

ColdFusion 2021 update 23 or later; ColdFusion 2023 update 17 or later; ColdFusion 2025 update 5 or later

  1. 1. Identify your current ColdFusion installation version by checking the ColdFusion Administrator or the version information in the installation directory.
  2. 2. Navigate to the Adobe ColdFusion downloads page or consult the official Adobe security bulletin at helpx.adobe.com for the specific patch information for CVE-2025-64897.
  3. 3. Download and install the appropriate ColdFusion update that addresses this vulnerability: For ColdFusion 2021, install version 2021.23 or later; For ColdFusion 2023, install version 2023.17 or later; For ColdFusion 2025, install version 2025.5 or later.
  4. 4. After applying the update, verify the installation by checking the ColdFusion Administrator to confirm the updated version number.
  5. 5. Test critical application workflows to ensure the update did not introduce any regressions.
Caveat Standard ColdFusion updates typically preserve configuration settings, but test in non-production environment first

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

Fix this in Coldfusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64897 — 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-64897 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