dbcve.org
ColdfusionApplication · Adobe

CVE-2025-49536

HIGH · 7.3 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 →
75/100
Remediation priority · High
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.2, 2023.14, 2021.20 and earlier are affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized access. Exploitation of this issue does not require user interaction. 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 · high confidence

ColdFusion versions 2025.2, 2023.14, 2021.20 and earlier contain an Incorrect Authorization vulnerability allowing low-privileged attackers to bypass security measures and gain unauthorized access. The vulnerable component is intended for internal IP addresses only and exploitation requires no user interaction.

MitigationUpgrade ColdFusion to the patched version (2025.3 or later for 2025.x, 2023.15 or later for 2023.x, 2021.21 or later for 2021.x). Ensure the affected component remains restricted to internal networks as per design.

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

CVSS:3.1/AV:A/AC:L/PR:L/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
    Log into the ColdFusion Administrator console and view the Server Settings > ColdFusion Updates page, or check the version.txt file in the cfroot directory
    Affected if Version is 2021.20 or earlier, 2023.14 or earlier, or 2025.2 or earlier
  2. Determine if the vulnerable component is network-accessible
    Review the web server or ColdFusion server configuration to identify which IP addresses the affected endpoint is bound to. Check network firewall rules and IIS/Apache binding configurations.
    Affected if The component is bound to or accessible from non-internal/external IP addresses (0.0.0.0 or public IP ranges)
  3. Review access logs for unauthorized access patterns
    Examine ColdFusion server access logs (default location: cfusion/logs or logs directory) for requests to internal-only endpoints from external IP addresses, especially those originating from low-privileged or unauthenticated sources
    Affected if Logs show requests to internal endpoints from IP addresses outside the trusted internal network range

You are affected if your ColdFusion version falls within the vulnerable ranges AND the internal-only component is exposed to non-internal networks.

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

Upgrade ColdFusion to the patched version (2025.3 or later for 2025.x, 2023.15 or later for 2023.x, 2021.21 or later for 2021.x). Ensure the affected component remains restricted to internal networks as per design.

Recommended fix High confidence

ColdFusion 2021.21+ (2021), 2023.15+ (2023), or 2025.3+ (2025)

  1. 1. Identify the currently installed ColdFusion version by checking the ColdFusion Administrator or the version.txt file in the installation directory
  2. 2. For ColdFusion 2021 users: Upgrade to version 2021.21 or later
  3. 3. For ColdFusion 2023 users: Upgrade to version 2023.15 or later
  4. 4. For ColdFusion 2025 users: Upgrade to version 2025.3 or later
  5. 5. Download the appropriate update from the Adobe ColdFusion downloads page (helpx.adobe.com)
  6. 6. Apply the update following Adobe's standard ColdFusion update installation procedures
  7. 7. After upgrading, verify the ColdFusion Administrator is accessible and the server starts successfully
  8. 8. Test critical applications to ensure functionality is intact after the update
Caveat Standard ColdFusion updates typically preserve configuration; however, test in non-production environment first as with any upgrade

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

Fix this in Coldfusion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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