dbcve.org
ColdfusionApplication · Adobe

CVE-2025-30290

HIGH · 8.7 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 →
93/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 2023.12, 2021.18, 2025.0 and earlier are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to a security feature bypass. A high privileged attacker could exploit this vulnerability to bypass security protections and gain unauthorized write and delete access. 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 · high confidence

Path traversal vulnerability in ColdFusion allows high-privileged attackers to bypass security protections and gain unauthorized write and delete access to restricted directories. No user interaction is required for exploitation.

MitigationApply vendor patches for ColdFusion versions 2023.12, 2021.18, 2025.0 and earlier to address the path traversal vulnerability and restrict file system access for privileged accounts.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/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 interface (typically at /cfadmin or /CFIDE/administrator/index.cfm) and locate the version information displayed on the login or welcome page. Alternatively, check the installer log files or the license file in the ColdFusion installation directory for the exact version number.
    Affected if The installed version is 2023.12 or earlier, 2021.18 or earlier, or 2025.0 or earlier (before applying vendor patches).
  2. Verify if high-privileged accounts exist
    In the ColdFusion Administrator, navigate to the User Manager or Security section and review the list of configured administrator accounts. Check whether RDS (Remote Development Services) is enabled or if any accounts have broad file system write or delete permissions.
    Affected if High-privileged ColdFusion administrator accounts or RDS-enabled accounts are present in the environment.
  3. Confirm web-exposed ColdFusion endpoints
    Review the web server configuration (IIS httpd.conf, Apache conf, or Tomcat server.xml) to identify all virtual directories or mappings that expose the ColdFusion context (CFIDE, cfadmin, or custom CFCs). Determine which endpoints are accessible over the network.
    Affected if ColdFusion administrative or scripting endpoints are accessible from the network without additional access controls.

The environment is affected if the installed ColdFusion version falls within 2021 (versions up to 2021.18), 2023 (versions up to 2023.12), or 2025 (versions up to 2025.0), and high-privileged accounts or exposed endpoints exist that could be leveraged for path traversal exploitation.

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 patches for ColdFusion versions 2023.12, 2021.18, 2025.0 and earlier to address the path traversal vulnerability and restrict file system access for privileged accounts.

Recommended fix Moderate confidence

ColdFusion 2023 Update 13+, ColdFusion 2021 Update 19+, or latest ColdFusion 2025 update (refer to Adobe hotfix bulletins)

  1. 1. Identify your current ColdFusion installation version by checking the ColdFusion Administrator or the version.xml file in the lib directory
  2. 2. For ColdFusion 2023: Upgrade to Update 13 or later from https://helpx.adobe.com/coldfusion/kb/coldfusion-2023-update-13.html
  3. 3. For ColdFusion 2021: Upgrade to Update 19 or later from https://helpx.adobe.com/coldfusion/kb/coldfusion-2021-update-19.html
  4. 4. For ColdFusion 2025: Upgrade to the latest available update from https://helpx.adobe.com/coldfusion/kb/coldfusion-2025-update.html
  5. 5. After applying the update, verify the installation through the ColdFusion Administrator > System Information page
  6. 6. Test critical file operations to confirm the path traversal protection is working as expected
  7. 7. Review and document the update for compliance purposes
Caveat Standard ColdFusion updates typically include cumulative hotfixes; review release notes for any behavior changes affecting your applications

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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