dbcve.org
ColdfusionApplication · Adobe

CVE-2025-43560

CRITICAL · 9.1 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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.1, 2023.13, 2021.19 and earlier are affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. A high-privileged attacker could leverage this vulnerability to bypass security mechanisms and execute code. 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 · moderate confidence

ColdFusion versions 2025.1, 2023.13, 2021.19 and earlier contain an improper input validation vulnerability that allows a high-privileged attacker to bypass security mechanisms and execute arbitrary code in the context of the current user. The vulnerability is exploitable without user interaction and involves a scope change.

MitigationApply Adobe ColdFusion security patches as soon as they are released. Prioritize patching production environments given the critical severity and potential for complete system compromise.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify installed ColdFusion version
    Access the ColdFusion Administrator console (typically at /cfide/administrator/) and navigate to the System Information or Settings page to view the exact version number. Alternatively, check the version.ini or registry entries on the server.
    Affected if The installed version is 2025.1, 2023.13, 2021.19 or any earlier version within the 2021, 2023, or 2025 product lines.
  2. Verify ColdFusion update patch status
    In ColdFusion Administrator, check the Server Updates or Updates section to confirm whether the security patches for CVE-2025-43560 have been applied.
    Affected if The patch status shows no security update applied or the installed version remains at or below the affected versions.
  3. Confirm high-privileged access exposure
    Review access logs and authentication records to determine whether ColdFusion Administrator, API endpoints, or other high-privileged administrative interfaces are exposed or accessible.
    Affected if High-privileged ColdFusion accounts or administrative interfaces are present and accessible, as the vulnerability requires a high-privileged attacker.

You are affected if your ColdFusion installation version is 2025.1, 2023.13, 2021.19 or earlier and the security patch for this CVE has not been applied.

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 Adobe ColdFusion security patches as soon as they are released. Prioritize patching production environments given the critical severity and potential for complete system compromise.

Recommended fix Moderate confidence

ColdFusion 2021.20+ (2021 branch), ColdFusion 2023.14+ (2023 branch), or ColdFusion 2025.2+ (2025 branch)

  1. 1. Back up your current ColdFusion installation, including all applications, databases, and configuration files.
  2. 2. Identify your current ColdFusion version by accessing the ColdFusion Administrator console.
  3. 3. For ColdFusion 2021 users: Upgrade to version 2021.20 or later (the next scheduled update after 2021.19).
  4. 4. For ColdFusion 2023 users: Upgrade to version 2023.14 or later (the next scheduled update after 2023.13).
  5. 5. For ColdFusion 2025 users: Upgrade to version 2025.2 or later (the next scheduled update after 2025.1).
  6. 6. Download the appropriate update from helpx.adobe.com/coldfusion/kb/coldfusion-2021-2023-2025-updates.html
  7. 7. Apply the update following Adobe's installation instructions.
  8. 8. After upgrading, verify that the ColdFusion services restart successfully.
Caveat Standard ColdFusion quarterly updates typically include security patches with minimal breaking changes; however, test in non-production environment before deploying to production

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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