CVE-2010-4330 json
Directory traversal vulnerability in includes/controller.php in Pulse CMS Basic before 1.2.9 allows remote attackers to include and execute…
published 15y ago modified 4mo ago also EUVD-2010-4302
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in includes/controller.php in Pulse CMS Basic before 1.2.9 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the p parameter to index.php.
Is CVE-2010-4330 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-15691)
- Published
Exploit prediction
2.63% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15691 Pulse CMS Basic - Local File Inclusion webapps, 2010-12-05
- osvdb.org http://osvdb.org/69622 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/45186 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/15691
exploit
-
osvdb.org
/69622
vdb-entry, exploit
-
securityfocus.com
/bid/45186
vdb-entry, exploit
-
secunia.com
/advisories/42462
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2010/3128
vdb-entry, vendor-advisory
- pulsecms.com /release-notes.php
-
securityfocus.com
/archive/1/515029/100/0/threaded
mailing-list
- uncompiled.com /2010/12/pulse-cms-basic-local-file-inclusion-vulnerability-cve-2010-4330/
Sources
- CVE List CVE-2010-4330
- NVD CVE-2010-4330
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.