dbcve.org
ColdfusionApplication · Adobe

CVE-2026-48324

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

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 is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could result in arbitrary code execution in the context of the current user. An attacker with high privileges could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.

In the news

Third-party coverage
Trending covered by 2 outlets this week · latest 1mo ago

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 confidence

ColdFusion contains an SQL injection vulnerability allowing authenticated attackers with high privileges to execute arbitrary code through improper neutralization of special elements in SQL commands. The vulnerability does not require user interaction and results in code execution in the context of the current user. Scope is changed, indicating the vulnerability impacts components beyond the vulnerable component itself.

MitigationApply vendor-supplied patches for ColdFusion when available; until then, implement input validation, use parameterized queries for all database operations, and restrict database account privileges to minimum necessary. Consider deploying a WAF as a compensating control.

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:= 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Determine installed ColdFusion version
    Access the ColdFusion Administrator interface and navigate to the 'System Information' or 'Settings' page to view the exact version number. Alternatively, check the version from the installation directory or by accessing the CFIDE/administrator/index.cfm page.
    Affected if The installed version is exactly 2023 or exactly 2025 (matches the affected versions = 2023 or = 2025)
  2. Verify high-privilege account existence
    Review user accounts in the ColdFusion Administrator under 'Security' > 'User Manager' or the underlying user database to identify accounts with Administrator-level or elevated privileges.
    Affected if High-privilege accounts exist in the ColdFusion installation (the vulnerability requires authenticated attackers with high privileges)
  3. Confirm database connectivity is enabled
    Check if the ColdFusion instance has configured data sources through the ColdFusion Administrator under 'Data & Services' > 'Data Sources' or by reviewing the 'datasources' configuration in the ColdFusion XML config files.
    Affected if Data sources are configured and the ColdFusion instance has database connectivity (SQL injection requires database interaction)
  4. Review for anomalous SQL query patterns
    Examine ColdFusion application logs (under /cfusion/logs or the logs directory) and database query logs for unexpected or malicious SQL statements, especially those containing UNION SELECT, EXEC, or system commands.
    Affected if Unusual SQL queries appear in logs indicating potential exploitation attempts

A ColdFusion installation is affected if it is exactly version 2023 or 2025 AND has high-privilege user accounts configured AND has database connectivity enabled.

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-supplied patches for ColdFusion when available; until then, implement input validation, use parameterized queries for all database operations, and restrict database account privileges to minimum necessary. Consider deploying a WAF as a compensating control.

Recommended fix Moderate confidence

Apply the latest ColdFusion 2023/2025 security hotfix from Adobe (check helpx.adobe.com for current patch)

  1. Check Adobe ColdFusion security bulletins at helpx.adobe.com for available hotfixes or patches
  2. Verify your current ColdFusion version by accessing the ColdFusion Administrator console
  3. Download and apply the latest ColdFusion security update from Adobe's official download center
  4. Restart the ColdFusion application server after applying the update
  5. Verify the patch was applied successfully by checking the ColdFusion version in the Administrator
Caveat Review Adobe release notes for any configuration or compatibility changes in the security update

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

Fix this in Coldfusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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