CVE-2025-49542
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 reflected Cross-Site Scripting (XSS) vulnerability. If an unauthenticated attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser, 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 · moderate confidenceColdFusion versions 2025.2, 2023.14, 2021.20 and earlier contain a reflected XSS vulnerability where unauthenticated attackers can craft malicious URLs that execute arbitrary JavaScript in victim browsers. The vulnerable component is restricted to internal IP addresses but can be exploited via social engineering to trick users into clicking malicious links.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed ColdFusion versionCheck the ColdFusion administrator console (通常在 /cfide/administrator/) 或查看安装目录中的 version.properties 文件。也可以通过命令行: cfconfig show 或查看 ColdFusion 安装日志。Affected if 版本号低于或等于 2021.20、2023.14 或 2025.2 (即所有受影响的版本)。如果无法确定具体版本号,请将当前版本与受影响范围进行比较。
-
定位受影响的组件该漏洞涉及 ColdFusion 中的反射机制。检查 ColdFusion 的 Web 根目录下的 cfide 目录,特别是 Administrator、corona 或其他管理相关的 URL 路径。确认是否存在未打补丁的 ColdFusion 实例仍在运行。Affected if 受影响的组件(通常是 ColdFusion Administrator 或相关管理端点)仍然可访问且未应用安全补丁。
-
检查网络访问控制审查防火墙规则、Web 服务器配置(如 Apache httpd.conf 或 IIS 配置)以及 ColdFusion 服务器的访问控制列表(ACL)。确认是否允许来自不受信任网络的访问。Affected if 受影响的 ColdFusion 组件可从外部 IP 地址访问,或者内部用户可能被社交工程攻击诱导点击恶意链接。
-
检查 Web 服务器日志中的可疑 URL检查 ColdFusion 的访问日志(通常位于 ColdFusion 安装目录的 logs 文件夹中)或 Web 服务器的错误/访问日志,查找包含<script>、javascript: 或其他 XSS 有效载荷的可疑请求模式。Affected if 日志中发现针对 ColdFusion 端点的异常或恶意构造的 URL 请求,这可能表明已尝试或正在进行利用。
如果 ColdFusion 版本在受影响范围内,且受影响的组件可通过网络访问,则存在被利用的风险;即使组件仅限内部 IP,通过社交工程的攻击仍可针对内部用户实施。
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 Adobe ColdFusion security patch when available; in the meantime, implement URL filtering at network perimeter, disable external access to the affected component, and educate users against clicking untrusted links.
ColdFusion 2021.21+ / 2023.15+ / 2025.3+ (latest available version for each respective release)
- Upgrade ColdFusion 2021 to version 2021.21 or later
- Upgrade ColdFusion 2023 to version 2023.15 or later
- Upgrade ColdFusion 2025 to version 2025.3 or later
- After upgrading, verify the fix by testing the previously vulnerable endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49542 — 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-49542 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