CVE-2007-6105 json
Multiple PHP remote file inclusion vulnerabilities in TalkBack 2.2.7 allow remote attackers to execute arbitrary PHP code via a URL in the…
published 2007-11-23 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6074
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.7%
- EPSS 6.7% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
Multiple PHP remote file inclusion vulnerabilities in TalkBack 2.2.7 allow remote attackers to execute arbitrary PHP code via a URL in the (1) language_file parameter to (a) comments-display-tpl.php and (b) addons/separate-comments-mod/my-comments-display-tpl.php and the (2) config[comments_form_tpl] parameter to comments-display-tpl.php.
Timeline
- First public exploit (EDB-4640)
- Published
Exploit prediction
6.72% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-4640 TalkBack 2.2.7 - Multiple Remote File Inclusions webapps, 2007-11-21
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-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/4640
exploit
-
secunia.com
/advisories/27767
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/484045/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/485662/100/100/threaded
mailing-list
-
securityfocus.com
/bid/26520
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/38596
vdb-entry
-
osvdb.org
/38815
vdb-entry
-
vupen.com
/english/advisories/2007/3963
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/38597
vdb-entry
- scripts.oldguy.us /forums/index.php/topic%2C290.0.html
-
osvdb.org
/38816
vdb-entry
Sources
- CVE List CVE-2007-6105
- NVD CVE-2007-6105
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.