CVE-2011-1669 json
Directory traversal vulnerability in wp-download.php in the WP Custom Pages module 0.5.0.1 for WordPress allows remote attackers to read ar…
published 2011-04-10 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1669
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 22.2%
- EPSS 22.2% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
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.
Patch / fix
Timeline
- First public exploit (EDB-17119)
- Published
Exploit prediction
22.16% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-17119 WordPress Plugin Custom Pages 0.5.0.1 - Local File Inclusion webapps, 2011-04-05
- Nuclei template WP Custom Pages 0.5.0.1 - Local File Inclusion (LFI) nuclei detection template
- securityfocus.com http://www.securityfocus.com/bid/47146 referenced PoC, tagged "exploit" by a source, unverified
- autosectools.com http://www.autosectools.com/Advisories/WordPress.WP.Custom.Pages.0.5.0.1_Local.File.Inclusion_169.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
securityfocus.com
/bid/47146
vdb-entry, exploit, patch
-
exploit-db.com
/exploits/17119
exploit
-
autosectools.com
/Advisories/WordPress.WP.Custom.Pages.0.5.0.1_Local.File.Inclusion_169.html
exploit
-
secunia.com
/advisories/43963
third-party-advisory, vendor-advisory
-
osvdb.org
/71707
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/66559
vdb-entry
Sources
- CVE List CVE-2011-1669
- NVD CVE-2011-1669
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.