# CVE-2024-20767: Adobe ColdFusion Improper Access Control

> Attackers can read or modify restricted files if the admin panel is exposed, requiring a patch for Adobe ColdFusion.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 16 Dec 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-r73p-8gx8-7pvg

## What is CVE-2024-20767?

CVE-2024-20767 is a high-severity missing authorization vulnerability in Adobe Coldfusion, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ColdFusion versions 2023.6, 2021.12 and earlier are affected by an Improper Access Control vulnerability that could result in arbitrary file system read. An attacker could leverage this vulnerability to access or modify restricted files. Exploitation of this issue does not require user interaction. Exploitation of this issue requires the admin panel be exposed to the internet.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-20767?

It affects 1 product.


Products: Adobe Coldfusion.

## How do I fix CVE-2024-20767?

No fix has been published for CVE-2024-20767 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 6 Jan 2025.

## Is CVE-2024-20767 being exploited?

Yes. Attackers have exploited CVE-2024-20767 in the wild since at least 16 Dec 2024.

Public exploit code:

- Exploit for CVE-2024-20767 - Adobe ColdFusion (github_poc): https://github.com/yoryio/CVE-2024-20767
- Exploit Toolkit for Adobe ColdFusion CVE-2024-20767 Vulnerability (github_poc): https://github.com/Chocapikk/CVE-2024-20767
- Proof of Concept for CVE-2024-20767. Arbitrary file read from Adobe ColdFusion  (github_poc): https://github.com/m-cetin/CVE-2024-20767
- Exploit for CVE-2024-20767 affecting Adobe ColdFusion (github_poc): https://github.com/GraySignal/CVE-2024-20767-Adobe-ColdFusion
- CVE-2024-20767 - Adobe Coldfusion Arbitrary File Read (metasploit)
- https://github.com/alm6no5/CVE-2024-20767 (github_poc): https://github.com/alm6no5/CVE-2024-20767

## Other vulnerabilities in Adobe Coldfusion

- [CVE-2026-48282](https://insights.sbomify.com/CVE-2026-48282/): Adobe ColdFusion Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-38203](https://insights.sbomify.com/CVE-2023-38203/): Adobe ColdFusion Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2023-29300](https://insights.sbomify.com/CVE-2023-29300/): Adobe ColdFusion Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2023-26359](https://insights.sbomify.com/CVE-2023-26359/): Adobe ColdFusion Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2018-15961](https://insights.sbomify.com/CVE-2018-15961/): Adobe ColdFusion Unrestricted File Upload (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20767 and fix it if it is affected.

What it is: CVE-2024-20767 is a high-severity missing authorization vulnerability in Adobe Coldfusion, published on 18 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-20767 in the wild since at least 16 Dec 2024.

Affected product: Adobe Coldfusion. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-20767/ (Markdown: https://insights.sbomify.com/CVE-2024-20767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20767
- OSV: https://osv.dev/vulnerability/CVE-2024-20767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-20767/
Summaries are generated and may contain mistakes; the official description above is the record.