CVE-2010-1267 json
Multiple directory traversal vulnerabilities in WebMaid CMS 0.2-6 Beta and earlier allow remote attackers to read arbitrary files via direc…
published 16y ago modified 4mo ago also EUVD-2010-1296
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 1
- Exploit-DB
Summary
Multiple directory traversal vulnerabilities in WebMaid CMS 0.2-6 Beta and earlier allow remote attackers to read arbitrary files via directory traversal sequences in the com parameter to (1) cContactus.php, (2) cGuestbook.php, and (3) cArticle.php.
Is CVE-2010-1267 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-11831)
- Published
Exploit prediction
2.77% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-11831 WebMaid CMS 0.2-6 Beta - Multiple Remote File Inclusions webapps, 2010-03-21
- securityfocus.com http://www.securityfocus.com/bid/38993 referenced PoC, tagged "exploit" by a source, unverified
- inj3ct0r.com http://inj3ct0r.com/exploits/11394 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1003-exploits/webmaid-rfilfi.txt 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
-
exploit-db.com
/exploits/11831
exploit
-
securityfocus.com
/bid/38993
vdb-entry, exploit
-
inj3ct0r.com
/exploits/11394
exploit
-
packetstormsecurity.org
/1003-exploits/webmaid-rfilfi.txt
exploit
-
vupen.com
/english/advisories/2010/0674
vdb-entry, vendor-advisory
Sources
- CVE List CVE-2010-1267
- NVD CVE-2010-1267
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.