dbcve.org
ColdfusionApplication · Adobe

CVE-2025-30287

HIGH · 8.2 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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 2023.12, 2021.18, 2025.0 and earlier are affected by an Improper Authentication vulnerability that could result in arbitrary code execution in the context of the current user. A low privileged attacker with local access could leverage this vulnerability to bypass security protections and execute code. Exploitation of this issue requires user interaction in that a victim must be coerced into performing actions within the application and scope is changed.

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 2023.12, 2021.18, 2025.0 and earlier contain an improper authentication vulnerability allowing low-privileged users with local access to bypass security protections and execute arbitrary code in the current user's context. The scope change indicates the vulnerability enables privilege escalation beyond the attacker's initial permissions.

MitigationApply the vendor-provided security patch or upgrade to a patched ColdFusion version. Review user privileges and restrict local access to minimize the attack surface while the patch is being deployed.

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

CVSS:3.1/AV:L/AC:L/PR:L/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
    Check the ColdFusion administrator interface (通常位于 /CFIDE/administrator/) 或查看ColdFusion安装目录中的version.txt或license.properties文件
    Affected if 版本为2021.18、2023.12、2025.0或更早版本（2021.x、2023.x、2025.x各分支的低于上述补丁级别的版本）
  2. 确认ColdFusion服务正在运行
    检查操作系统进程列表或服务状态，确认ColdFusion Application Server服务处于活动状态
    Affected if ColdFusion服务正在运行且版本处于受影响范围内
  3. 检查CFIDE目录完整性
    检查Web根目录下CFIDE目录是否存在且未被篡改，注意此漏洞可能涉及本地访问场景下的认证绕过
    Affected if CFIDE目录存在且服务运行，但版本在受影响范围内
  4. 验证当前补丁状态
    通过ColdFusion Administrator的更新检查功能或查看安装目录下的补丁记录文件
    Affected if 无法找到针对CVE-2025-30287的补丁更新或补丁级别低于2021.18/2023.12/2025.0对应版本

如果正在运行的ColdFusion版本为2021.18、2023.12、2025.0或更早版本，则当前环境存在该认证绕过漏洞的风险

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-provided security patch or upgrade to a patched ColdFusion version. Review user privileges and restrict local access to minimize the attack surface while the patch is being deployed.

Recommended fix Moderate confidence

ColdFusion 2023 Update 13+ / ColdFusion 2021 Update 19+ / ColdFusion 2025 Update 1+

  1. 1. Identify the currently installed ColdFusion version by checking the ColdFusion Administrator console or the version information in the installation directory.
  2. 2. For ColdFusion 2023: Upgrade to ColdFusion 2023 Update 13 or later.
  3. 3. For ColdFusion 2021: Upgrade to ColdFusion 2021 Update 19 or later.
  4. 4. For ColdFusion 2025: Upgrade to ColdFusion 2025 Update 1 or later.
  5. 5. Download the appropriate update from the official Adobe ColdFusion downloads page (helpx.adobe.com).
  6. 6. Back up the ColdFusion instance, including the installation directory and any custom configurations, before applying the update.
  7. 7. Apply the update following Adobe's standard ColdFusion update installation procedures.
  8. 8. After updating, verify the ColdFusion services restart successfully and confirm the new version number in the ColdFusion Administrator.
Caveat Standard ColdFusion updates typically retain backward compatibility; however, test your applications after applying the update to ensure custom code and configurations work correctly.

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
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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