# CVE-2011-4543: Path traversal in n/a

> Remote attackers with admin access can execute arbitrary local files via directory traversal in osCommerce admin pages.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c4h4-9rv6-5g6h

## What is CVE-2011-4543?

CVE-2011-4543 is a high-severity path traversal vulnerability in Oscommerce Oscommerce, published on 5 Dec 2011. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in osCommerce 3.0.2 allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in the (1) set or (2) module parameter to (a) OM/Core/Site/Admin/Application/templates_modules/pages/info.php, (b) OM/Core/Site/Admin/Application/templates_modules/pages/edit.php, or (c) OM/Core/Site/Admin/Application/templates_modules/pages/uninstall.php; the (3) set parameter to OM/Core/Site/Admin/Application/templates_modules/pages/main.php; the module parameter to (4) OM/Core/Site/Admin/Application/modules_order_total/pages/edit.php, (5) OM/Core/Site/Admin/Application/modules_order_total/pages/uninstall.php, (6) OM/Core/Site/Admin/Application/modules_order_total/pages/info.php, (7) OM/Core/Site/Admin/Application/modules_geoip/pages/edit.php, (8) OM/Core/Site/Admin/Application/modules_geoip/pages/uninstall.php, (9) OM/Core/Site/Admin/Application/images/pages/main.php, (10) OM/Core/Site/Admin/Application/modules_shipping/pages/edit.php, or (11) OM/Core/Site/Admin/Application/modules_shipping/pages/uninstall.php; the filter parameter to (12) OM/Core/Site/Admin/Application/templates_modules_layout/pages/main.php, (13) OM/Core/Site/Admin/Application/templates_modules_layout/pages/new.php, or (14) OM/Core/Site/Admin/Application/templates_modules_layout/pages/edit.php; or the template parameter to (15) OM/Core/Site/Admin/Application/templates/pages/info.php, (16) OM/Core/Site/Admin/Application/templates/pages/edit.php, or (17) OM/Core/Site/Admin/Application/templates/pages/uninstall.php.

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

## Which versions are affected by CVE-2011-4543?

It affects 1 product.


Products: Oscommerce Oscommerce.

## How do I fix CVE-2011-4543?

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

## Is CVE-2011-4543 being exploited?

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

## Other vulnerabilities in Oscommerce Oscommerce

- [CVE-2020-23360](https://insights.sbomify.com/CVE-2020-23360/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-27976](https://insights.sbomify.com/CVE-2020-27976/): Command injection in n/a (critical 9.8)
- [CVE-2019-25495](https://insights.sbomify.com/CVE-2019-25495/): osCommerce 2.3.4.1 SQL Injection via reviews_id Parameter (high 8.8)
- [CVE-2019-25496](https://insights.sbomify.com/CVE-2019-25496/): osCommerce 2.3.4.1 SQL Injection via products_id Parameter (high 8.8)
- [CVE-2019-25497](https://insights.sbomify.com/CVE-2019-25497/): osCommerce 2.3.4.1 SQL Injection via currency Parameter (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4543 and fix it if it is affected.

What it is: CVE-2011-4543 is a high-severity path traversal vulnerability in Oscommerce Oscommerce, published on 5 Dec 2011. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4543 in the wild and no public exploit code.

Affected product: Oscommerce Oscommerce. 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-2011-4543/ (Markdown: https://insights.sbomify.com/CVE-2011-4543/index.md)
```

## Sources

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

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