dbcve.org
ColdfusionApplication · Adobe

CVE-2025-61813

HIGH · 7.4 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 →
81/100
Remediation priority · High
Remotely reachable No privileges

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 Restriction of XML External Entity Reference ('XXE') vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files on the server. Exploitation of this issue does requires 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 confidence

ColdFusion versions 2025.4, 2023.16, 2021.22 and earlier contain an XXE vulnerability allowing attackers to read arbitrary files from the server's file system through malicious XML input with crafted external entity references.

MitigationApply the vendor-supplied patches for this vulnerability (2025.5, 2023.17, 2021.23 or later) and consider disabling external entity processing in XML parsers as a defense-in-depth measure.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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. Determine ColdFusion installed version
    Access the ColdFusion Administrator console (usually at /cfadmin or /CFIDE/administrator) and check the version displayed on the login page or in the Server Settings > ColdFusion Updates section. Alternatively, check the version file in the ColdFusion installation directory (version.ini or similar) or run: cfconfig show version from the command line if cfconfig is installed.
    Affected if The installed version is 2021.22 or earlier, 2023.16 or earlier, or 2025.4 or earlier.
  2. Verify XML parsing functionality is accessible
    Identify endpoints or features that accept XML input in your ColdFusion application. Common vectors include: web services (WSDL imports), file upload handlers that process XML, API endpoints accepting XML payloads, or any cfajax, cfxml, or XMLParse() usage. Review your application code for cfxml tags, XmlParse() function calls, or SOAP/REST endpoints accepting XML content types.
    Affected if XML parsing functionality is exposed and accepts untrusted input without disabling external entity processing.
  3. Check for external entity processing in XML parsers
    Inspect XML parser configuration in your ColdFusion environment. Look for: 1) The jvm.config file in the ColdFusion runtime directory for custom parser settings, 2) Any custom XML parser initialization code in your application that may enable external entities, 3) The underlying Java parser settings if accessible. Search codebase for XmlHttpRequest, DocType, or SYSTEM keyword usage in XML-related code.
    Affected if External entity processing is enabled in XML parsers or no XXE protection is implemented in XML-handling code.

Your environment is affected if you are running ColdFusion 2021.22 or earlier, 2023.16 or earlier, or 2025.4 or earlier AND have XML parsing functionality that processes untrusted input with external entities enabled.

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 patches for this vulnerability (2025.5, 2023.17, 2021.23 or later) and consider disabling external entity processing in XML parsers as a defense-in-depth measure.

Recommended fix High confidence

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

  1. 1. Identify the currently installed ColdFusion version by checking the ColdFusion Administrator or the version number in the installation directory.
  2. 2. For ColdFusion 2021: Upgrade to version 2021.23 or later.
  3. 3. For ColdFusion 2023: Upgrade to version 2023.17 or later.
  4. 4. For ColdFusion 2025: Upgrade to version 2025.5 or later.
  5. 5. Download the appropriate update from the Adobe ColdFusion downloads page (helpx.adobe.com) or use the ColdFusion Administrator's auto-update feature.
  6. 6. Before applying the update, back up the ColdFusion installation directory, especially the lib and lib\wwwroot\WEB-INF directories.
  7. 7. Apply the update following Adobe's standard installation process.
  8. 8. Restart the ColdFusion application server after the update completes.
Caveat Standard ColdFusion update; review Adobe's release notes for any configuration or compatibility notes for the specific update version

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-61813 — 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-61813 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