dbcve.org
ColdfusionApplication · Adobe

CVE-2025-24447

CRITICAL · 9.1 CVSS v3.1 Published 2025-04-08
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 2023.12, 2021.18, 2025.0 and earlier are affected by a Deserialization of Untrusted Data vulnerability that could result in arbitrary code execution in the context of the current user resulting in a High impact to Confidentiality and Integrity. Exploitation of this issue does not require 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 · high confidence

ColdFusion versions 2023.12, 2021.18, 2025.0 and earlier contain a deserialization vulnerability where untrusted data is processed without proper validation, allowing an attacker to execute arbitrary code in the context of the ColdFusion service user. The flaw is exploitable without any authentication or user interaction, making it remotely exploitable.

MitigationApply the vendor-supplied patch or upgrade to a supported ColdFusion version that addresses this deserialization flaw. Verify the fix does not introduce regressions in existing ColdFusion applications.

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. Identify installed ColdFusion version
    Access the ColdFusion Administrator console (usually at /cfide/administrator/ or /CFRame/index.cfm) and check the version displayed on the login or about page. Alternatively, check the version file in the ColdFusion installation directory or registry on Windows.
    Affected if The installed version is 2023.12 or earlier, 2021.18 or earlier, or 2025.0 (any build), or if the version cannot be determined but the product is present.
  2. Check ColdFusion service status
    On Windows, open Services console and locate 'ColdFusion 2023', 'ColdFusion 2021', or 'ColdFusion 2025' service. On Linux/Unix, check for coldfusion processes running.
    Affected if The ColdFusion service is running and the version falls within the affected ranges.
  3. Verify patch status via hotfix list
    In ColdFusion Administrator, navigate to the Updates or Hotfixes section to view applied patches. Compare the installed version number against the fixed releases (2023.13 and later, 2021.19 and later, 2025.1 and later).
    Affected if No hotfix or patch matching the fixed versions is installed, or the patch list is empty/unavailable.
  4. Check for exposed BlazeDS/AMF endpoints
    Search web server logs and ColdFusion configuration for access to /flex2gateway/, /messagebroker/*, or /cfapi/ endpoints. These are common paths for AMF/BlazeDS services that handle deserialized data.
    Affected if These endpoints are accessible remotely without authentication and the ColdFusion version is within the affected range.

If ColdFusion 2023.12 or earlier, 2021.18 or earlier, or 2025.0 is running without the vendor patch applied, the environment is vulnerable to unauthenticated remote code execution via deserialization.

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 vendor-supplied patch or upgrade to a supported ColdFusion version that addresses this deserialization flaw. Verify the fix does not introduce regressions in existing ColdFusion applications.

Recommended fix Moderate confidence

Upgrade to ColdFusion 2023.13 or later, ColdFusion 2021.19 or later, or ColdFusion 2025.1 or later depending on your major version

  1. 1. Identify the currently installed ColdFusion version by checking the ColdFusion Administrator console or the version information in the installation directory.
  2. 2. Navigate to the Adobe ColdFusion security bulletins page at helpx.adobe.com to obtain the latest security updates.
  3. 3. Download the appropriate ColdFusion update for your version: For ColdFusion 2023, obtain version 2023.13 or later; For ColdFusion 2021, obtain version 2021.19 or later; For ColdFusion 2025, obtain version 2025.1 or later.
  4. 4. Before applying the update, perform a complete backup of the ColdFusion installation directory, including the cfusion directory and any custom configurations.
  5. 5. Stop the ColdFusion application server services to ensure a clean update process.
  6. 6. Apply the downloaded security update following Adobe's official installation instructions.
  7. 7. After installation, verify that the ColdFusion services start successfully.
  8. 8. Review the ColdFusion Administrator to confirm the updated version number reflects the patched release.
Caveat Standard ColdFusion quarterly updates typically maintain backward compatibility; test in staging before production deployment

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

Fix this in Coldfusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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