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

> Remote attackers can read arbitrary files via directory traversal in the Jstore component for Joomla.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 16 Sep 2024
- **Also known as:** GHSA-q5xj-3wxr-5xw3

## What is CVE-2010-5286?

CVE-2010-5286 is a critical 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 Jstore (com_jstore) component for Joomla! allows remote attackers to read arbitrary files and possibly have unspecified other impact via a .. (dot dot) in the controller parameter to index.php.

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

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

It affects 1 product.


Products: Joobi Com Jstore.

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

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

## Is CVE-2010-5286 being exploited?

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

Public exploit code:

- Joomla! Component Jstore - 'Controller' Local File Inclusion (exploitdb)
- Joomla! Component Jstore - 'Controller' Local File Inclusion (nuclei): http/cves/2010/CVE-2010-5286.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2010-5286 is a critical 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-5286 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-5286/ (Markdown: https://insights.sbomify.com/CVE-2010-5286/index.md)
```

## Sources

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

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