CVE-2025-49545
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 · uneditedColdFusion versions 2025.2, 2023.14, 2021.20 and earlier are affected by a Server-Side Request Forgery (SSRF) vulnerability that could lead to arbitrary file system read. A high-privilege authenticated attacker can force the application to make arbitrary requests via injection of URLs. Exploitation of this issue does not require 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 · high confidenceColdFusion versions prior to 2025.2, 2023.14, and 2021.20 contain a Server-Side Request Forgery (SSRF) vulnerability allowing a high-privilege authenticated attacker to inject arbitrary URLs and cause the application to make outbound requests, potentially leading to arbitrary file system read access through internal services.
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= 2021= 2023= 2025CVSS 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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ColdFusion installation and versionLocate the ColdFusion installation directory. Check the version by viewing the 'version.properties' or 'version.txt' file in the ColdFusion home directory, or by accessing the ColdFusion Administrator interface and reviewing the System Information page.Affected if The installed version is any release prior to 2025.2 (for ColdFusion 2025), 2023.14 (for ColdFusion 2023), or 2021.20 (for ColdFusion 2021).
-
Verify ColdFusion Administrator accessConfirm whether the ColdFusion Administrator console (typically at /cfide/administrator/ or /cfadmin/) is accessible over the network. Check network firewall rules and IIS/Apache configuration for any URL access controls.Affected if The ColdFusion Administrator interface is exposed to untrusted networks without IP restrictions or VPN requirements.
-
Confirm authentication to ColdFusion AdministratorDetermine if there are existing user accounts in the ColdFusion Administrator with high-privilege access (such as Administrator-level roles). Review the user management section in the ColdFusion Administrator.Affected if High-privilege authenticated users exist in the ColdFusion environment, allowing them to access features that could trigger the SSRF vulnerability.
-
Check for exposure of internal service endpointsReview whether internal network services (such as internal APIs, database servers, or file servers) are accessible from the ColdFusion server without authentication. Examine any configured data sources or server-specific configurations.Affected if Internal services are accessible from the ColdFusion server without proper authentication, which could be targeted by the SSRF flaw to achieve unauthorized file system read access.
A user is affected if their ColdFusion installation version is 2021.x prior to update 20, 2023.x prior to update 14, or 2025.x prior to version 2, AND the ColdFusion Administrator is accessible to an attacker with high-privilege credentials.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patches for ColdFusion versions 2025.2, 2023.14, and 2021.20. Additionally, enforce strict network segmentation and restrict internal service access to further limit the impact of SSRF attacks.
ColdFusion 2021 update to 2021.21+, ColdFusion 2023 update to 2023.15+, ColdFusion 2025 update to 2025.3+
- Identify your current ColdFusion version by checking the ColdFusion Administrator or the version info in the installation directory
- For ColdFusion 2021: Upgrade to version 2021.21 or later
- For ColdFusion 2023: Upgrade to version 2023.15 or later
- For ColdFusion 2025: Upgrade to version 2025.3 or later
- Download the updates from the Adobe ColdFusion downloads page (https://helpx.adobe.com/coldfusion/downloads.html) or use the ColdFusion Administrator's auto-update feature
- Apply the update following Adobe's standard ColdFusion update installation procedure
- Restart the ColdFusion services after the update completes
- Verify the installation was successful by checking the version in ColdFusion Administrator
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49545 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49545 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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