CVE-2026-48307
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.9, 2023.20 and earlier are affected by a reflected Cross-Site Scripting (XSS) vulnerability. An attacker could exploit this vulnerability to inject malicious scripts into a web page, potentially resulting in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious link. Scope is changed.
In the news
Third-party coverage- Adobe Patches 7 CVSS 10.0 Flaws in ColdFusion and Campaign Classic
- Adobe fixed multiple maximum-severity flaws in ...
- Adobe Patches Critical ColdFusion, Campaign Classic Vulnerabilities
Surfaced from public web coverage — external links open in a new tab.
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 confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in Adobe ColdFusion versions 2025.9, 2023.20 and earlier. Attackers can craft malicious URLs containing JavaScript payloads that execute in the victim's browser when clicked, potentially achieving arbitrary code execution in the user's context. The scope change indicates the vulnerability can impact resources beyond the vulnerable ColdFusion component.
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= 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ColdFusion versionCheck the ColdFusion administrator interface (typically at /CFIDE/administrator/index.cfm) or inspect the cfadmin web application. Alternatively, check the version file in the ColdFusion installation directory or review server startup logs for the version string.Affected if The installed version is ColdFusion 2023.20 or earlier, or ColdFusion 2025.9 or earlier.
-
Confirm ColdFusion web interface is exposedVerify that the ColdFusion administrator or application endpoints are accessible over HTTP/HTTPS by attempting to access common ColdFusion paths such as /CFIDE/administrator/, /index.cfm, or any custom ColdFusion (.cfm) applications.Affected if ColdFusion web endpoints are externally accessible without authentication restrictions.
-
Inspect URL parameter handling in ColdFusion applicationsReview application code (CFM files) for CFQUERY, CFLOCATION, or output statements that directly use URL parameters (e.g., #URL.paramname#) without using HTMLEditFormat(), EncodeForHTML(), or similar sanitization functions.Affected if URL parameters are reflected in output without proper encoding or validation.
-
Check for missing input validation filtersExamine any existing web application firewall (WAF) configurations, ColdFusion administrator security settings, or application-level input validation for URL parameters. Look for absence of parameter validation rules.Affected if No input validation or output encoding is implemented for URL parameters in the application.
A system is affected if it runs an unpatched ColdFusion 2023 version 20 or earlier, or ColdFusion 2025 version 9 or earlier, with accessible web endpoints that reflect URL parameters without sanitization.
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 patch when released. Until then, implement URL parameter validation and output encoding on affected endpoints, and educate users to avoid clicking untrusted links.
Upgrade to ColdFusion 2023 Update 21+ or ColdFusion 2025 Update 10+ (or the latest available respective version)
- 1. Identify the current ColdFusion version by checking the ColdFusion Administrator or the version information in the installation
- 2. For ColdFusion 2023 users: Upgrade to ColdFusion 2023 version 21 or later (a version newer than 2023.20)
- 3. For ColdFusion 2025 users: Upgrade to ColdFusion 2025 version 10 or later (a version newer than 2025.9)
- 4. Obtain the latest ColdFusion installer from the Adobe ColdFusion downloads page (https://www.adobe.com/products/coldfusion/download.html)
- 5. Before applying in production, test the upgrade in a non-production/staging environment to verify compatibility
- 6. After upgrade, clear browser caches and test that the application functions correctly
- 7. Monitor Adobe security bulletins for any additional required patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48307 — 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-2026-48307 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