# CVE-2010-2861: Adobe ColdFusion Directory Traversal

> Remote attackers can read arbitrary files via directory traversal in the administrator console of Adobe ColdFusion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2010
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-x38c-xq6c-937h

## What is CVE-2010-2861?

CVE-2010-2861 is a high-severity path traversal vulnerability in Adobe Coldfusion, published on 11 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in the administrator console in Adobe ColdFusion 9.0.1 and earlier allow remote attackers to read arbitrary files via the locale parameter to (1) CFIDE/administrator/settings/mappings.cfm, (2) logging/settings.cfm, (3) datasources/index.cfm, (4) j2eepackaging/editarchive.cfm, and (5) enter.cfm in CFIDE/administrator/.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2010-2861?

It affects 1 product.


Products: Adobe Coldfusion.

## How do I fix CVE-2010-2861?

No fix has been published for CVE-2010-2861 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2010-2861 being exploited?

Yes. Attackers have exploited CVE-2010-2861 in the wild since at least 25 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Adobe ColdFusion - Directory Traversal (exploitdb)
- Adobe ColdFusion - Directory Traversal (Metasploit) (exploitdb)
- Redux Python3 Version of CVE-2010-2861 (github_poc): https://github.com/greysneakthief/14641-v2
- Vulhub coldfusion/CVE-2010-2861: Adobe ColdFusion 8 Directory Traversal (CVE-2010-2861), run with Isoloom (github_poc): https://github.com/CyberCTF/vulhub-coldfusion-cve-2010-2861
- ColdFusion Server Check (metasploit)
- Adobe ColdFusion 8.0/8.0.1/9.0/9.0.1 LFI (nuclei): http/cves/2010/CVE-2010-2861.yaml

## 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-2010-2861 and fix it if it is affected.

What it is: CVE-2010-2861 is a high-severity path traversal vulnerability in Adobe Coldfusion, published on 11 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2010-2861 in the wild since at least 25 Mar 2022, including in ransomware campaigns.

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-2010-2861/ (Markdown: https://insights.sbomify.com/CVE-2010-2861/index.md)
```

## Sources

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

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