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

> Remote attackers can read arbitrary files via directory traversal in the IBrowser TinyMCE plugin when magic_quotes_gpc is disabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-44fg-qr23-qj5r

## What is CVE-2010-5281?

CVE-2010-5281 is a medium-severity path traversal vulnerability in n/a, published on 26 Nov 2012. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in ibrowser.php in the CMScout 2.09 IBrowser TinyMCE Plugin 1.4.1, when magic_quotes_gpc is disabled, allows remote attackers to read arbitrary files via a .. (dot dot) in the lang parameter.  NOTE: some of these details are obtained from third party information.

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

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

It affects 1 product.


Products: Net4visions Ibrowser.

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

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

## Is CVE-2010-5281 being exploited?

There is no known exploitation of CVE-2010-5281 in the wild and no public exploit code.

Public exploit code:

- iBrowser Plugin 1.4.1 - 'lang' Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-5281 is a medium-severity path traversal vulnerability in n/a, published on 26 Nov 2012. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-5281 in the wild and no public exploit code.

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

## Sources

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

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