dbcve.org
ColdfusionApplication · Adobe

CVE-2025-49537

HIGH · 7.9 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High

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.2, 2023.14, 2021.20 and earlier are affected by an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability that could lead to arbitrary code execution by a high-privileged attacker. Exploitation of this issue requires user interaction and scope is changed. The vulnerable component is restricted to internal IP addresses.

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.2, 2023.14, 2021.20 and earlier contain an OS command injection vulnerability allowing arbitrary code execution. The vulnerable component is bound to internal IP addresses only, and exploitation requires both a high-privileged attacker and user interaction, with scope changed indicating impact beyond the affected component.

MitigationApply the vendor patch for this OS command injection vulnerability by upgrading ColdFusion to the fixed versions. Until patched, ensure the affected component remains network-isolated to internal IPs and enforce least-privilege access controls.

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
Adjacent
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/UI:R/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 interface or check the version file in the ColdFusion installation directory. The version is typically shown in the Administrator landing page or可通过 cfconfig 或 coldfusion 版本查询命令获取。
    Affected if 版本低于 2021.20、2023.14 或 2025.2（即所有列出的受影响版本）
  2. Verify network binding of the vulnerable component
    检查 ColdFusion 服务器的网络配置，确认易受攻击的组件是否仅绑定到内部 IP 地址（127.0.0.1 或内部网络 IP）。检查服务器配置文件中的监听地址设置。
    Affected if 该组件绑定到可从外部访问的 IP 地址或公开暴露在网络端口上
  3. Confirm high-privileged access exists
    审查 ColdFusion 管理员账户和用户权限配置。检查是否存在具有管理权限的用户账户，以及这些账户是否可通过网络访问。
    Affected if 存在高权限管理员账户且该账户可从非内部网络访问
  4. Check for user interaction vectors
    审查 ColdFusion 应用程序中用户可提交输入的功能，特别是涉及文件处理、数据查询或可触发后端命令执行的端点。
    Affected if 应用程序接受用户输入并将其传递到可能触发 OS 命令执行的组件中

如果 ColdFusion 版本低于 2021.20、2023.14 或 2025.2，且易受攻击的组件绑定到非内部 IP 地址或可被高权限用户访问，则该环境可能受此 CVE 影响。

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 patch for this OS command injection vulnerability by upgrading ColdFusion to the fixed versions. Until patched, ensure the affected component remains network-isolated to internal IPs and enforce least-privilege access controls.

Recommended fix Moderate confidence

ColdFusion 2021 Update 21+, ColdFusion 2023 Update 15+, ColdFusion 2025 Update 3+

  1. 1. Identify the currently installed ColdFusion version by checking the ColdFusion Administrator or the version file
  2. 2. For ColdFusion 2021: Upgrade to Update 21 or later
  3. 3. For ColdFusion 2023: Upgrade to Update 15 or later
  4. 4. For ColdFusion 2025: Upgrade to Update 3 or later
  5. 5. After upgrading, verify the ColdFusion Administrator shows the new version number
  6. 6. Test critical applications to ensure functionality is maintained after the update
  7. 7. Review Adobe ColdFusion security bulletin for any additional post-upgrade configuration steps
Caveat Review Adobe release notes for each update as minor breaking changes in functionality or deprecated features may occur

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