# CVE-2011-10009: S40 CMS 0.4.2 Path Traversal

> Attackers can remotely access arbitrary files outside the web root via unsanitized input in S40 CMS, leading to information disclosure.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-2gj5-g2gq-97mp

## What is CVE-2011-10009?

CVE-2011-10009 is a high-severity path traversal vulnerability in S40 CMS, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

S40 CMS v0.4.2 contains a path traversal vulnerability in its index.php page handler. The p parameter is not properly sanitized, allowing attackers to traverse the file system and access arbitrary files outside the web root. This can be exploited remotely without authentication by appending traversal sequences and a null byte to bypass file extension checks.

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

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


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

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

## Is CVE-2011-10009 being exploited?

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

Public exploit code:

- S40 0.4.2 CMS Directory Traversal Vulnerability (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-10009 is a high-severity path traversal vulnerability in S40 CMS, published on 13 Aug 2025. 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-2011-10009 exists.

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

## Sources

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

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