CVE-2007-6581 json
Multiple directory traversal vulnerabilities in Social Engine 2.0 allow remote attackers to include and execute arbitrary local files via a…
published 2007-12-28 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6547
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
Multiple directory traversal vulnerabilities in Social Engine 2.0 allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in the global_lang parameter to (1) header_album.php, (2) header_blog.php, or (3) header_group.php; or (4) admin_header_album.php, (5) admin_header_blog.php, or (6) admin_header_group.php in admin/.
Timeline
- First public exploit (EDB-4767)
- Published
Exploit prediction
3.54% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-4767 Social Engine 2.0 - Multiple Local File Inclusions webapps, 2007-12-21
- securityfocus.com http://www.securityfocus.com/bid/26990 referenced PoC, tagged "exploit" by a source, unverified
- inj3ct-it.org http://www.inj3ct-it.org/exploit/socialengine2.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/4767
exploit
-
securityfocus.com
/bid/26990
vdb-entry, exploit
-
inj3ct-it.org
/exploit/socialengine2.txt
exploit
-
osvdb.org
/40371
vdb-entry
-
osvdb.org
/40373
vdb-entry
-
osvdb.org
/40370
vdb-entry
-
osvdb.org
/40374
vdb-entry
-
osvdb.org
/40375
vdb-entry
-
osvdb.org
/40372
vdb-entry
Sources
- CVE List CVE-2007-6581
- NVD CVE-2007-6581
Fencer Vulns 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.