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

> Remote attackers can read arbitrary files via directory traversal in the WP Custom Pages plugin, exposing sensitive data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-876x-3ww3-wx43

## What is CVE-2011-1669?

CVE-2011-1669 is a medium-severity path traversal vulnerability in n/a, published on 10 Apr 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in wp-download.php in the WP Custom Pages module 0.5.0.1 for WordPress allows remote attackers to read arbitrary files via ..%2F (encoded dot dot) sequences in the url parameter.

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

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

It affects 1 product.


Products: Mikoviny Wp Custom Pages.

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

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

## Is CVE-2011-1669 being exploited?

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

Public exploit code:

- WordPress Plugin Custom Pages 0.5.0.1 - Local File Inclusion (exploitdb)
- WP Custom Pages 0.5.0.1 - Local File Inclusion (LFI) (nuclei): http/cves/2011/CVE-2011-1669.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1669 is a medium-severity path traversal vulnerability in n/a, published on 10 Apr 2011. 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-1669 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-2011-1669/ (Markdown: https://insights.sbomify.com/CVE-2011-1669/index.md)
```

## Sources

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

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