# CVE-2009-1936: Path traversal in n/a

> Remote attackers can bypass protection mechanisms to execute arbitrary code or read files via path traversal in cpCommerce.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2009
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-492m-hh57-3gv9

## What is CVE-2009-1936?

CVE-2009-1936 is a critical path traversal vulnerability in n/a, published on 5 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

_functions.php in cpCommerce 1.2.x, possibly including 1.2.9, sends a redirect but does not exit when it is called directly, which allows remote attackers to bypass a protection mechanism to conduct remote file inclusion and directory traversal attacks, execute arbitrary PHP code, or read arbitrary files via the GLOBALS[prefix] parameter, a different vector than CVE-2003-1500.

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

## Which versions are affected by CVE-2009-1936?

It affects 1 product.


Products: Cpcommerce Project Cpcommerce.

## How do I fix CVE-2009-1936?

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

## Is CVE-2009-1936 being exploited?

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

Public exploit code:

- CPCommerce 1.2.x - 'GLOBALS[prefix]' Arbitrary File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1936 and fix it if it is affected.

What it is: CVE-2009-1936 is a critical path traversal vulnerability in n/a, published on 5 Jun 2009. 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-2009-1936 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-2009-1936/ (Markdown: https://insights.sbomify.com/CVE-2009-1936/index.md)
```

## Sources

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

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