# CVE-2010-5280: Path traversal in n/a

> Remote attackers can exploit a directory traversal flaw in the Joomla CBE plugin to include arbitrary local files and execute code.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8vq6-8xq6-mp5r

## What is CVE-2010-5280?

CVE-2010-5280 is a high-severity path traversal vulnerability in n/a, published on 26 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in the Community Builder Enhanced (CBE) (com_cbe) component 1.4.8, 1.4.9, and 1.4.10 for Joomla! allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the tabname parameter in a userProfile action to index.php.  NOTE: this can be leveraged to execute arbitrary code by using the file upload feature.

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

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

It affects 1 product.


Products: Joomla-Cbe Com Cbe.

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

No fix has been published for CVE-2010-5280 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-5280 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-5280 exists.

Public exploit code:

- Joomla! Component Community Builder Enhanced (CBE) 1.4.8/1.4.9/1.4.10 - Local File Inclusion / Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5280 and fix it if it is affected.

What it is: CVE-2010-5280 is a high-severity path traversal vulnerability in n/a, published on 26 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-5280 exists.

Affected product: n/a. 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-5280/ (Markdown: https://insights.sbomify.com/CVE-2010-5280/index.md)
```

## Sources

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

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