CVE-2006-6958 json
Multiple PHP remote file inclusion vulnerabilities in phpBlueDragon 2.9.1 allow remote attackers to execute arbitrary PHP code via a URL in…
published 2007-01-29 19 y ago modified 2026-06-16 4 mo ago also EUVD-2006-6941
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.9%
- EPSS 8.9% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
Multiple PHP remote file inclusion vulnerabilities in phpBlueDragon 2.9.1 allow remote attackers to execute arbitrary PHP code via a URL in the vsDragonRootPath parameter to (1) team_admin.php, (2) rss_admin.php, (3) manual_admin.php, and (4) forum_admin.php in includes/root_modules/, a different set of vectors than CVE-2006-3076.
Timeline
- First public exploit (EDB-28098)
- Published
Exploit prediction
8.87% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-28098 PHP Blue Dragon CMS 2.9.1 - Multiple Remote File Inclusions webapps, 2006-06-22
- packetstormsecurity.org http://packetstormsecurity.org/0606-exploits/phpbluedragon-2.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/18609 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
packetstormsecurity.org
/0606-exploits/phpbluedragon-2.txt
exploit
-
securityfocus.com
/bid/18609
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/27152
vdb-entry
-
osvdb.org
/27678
vdb-entry
-
osvdb.org
/27676
vdb-entry
-
osvdb.org
/27677
vdb-entry
-
securityreason.com
/securityalert/2193
third-party-advisory
-
osvdb.org
/27679
vdb-entry
-
securityfocus.com
/archive/1/438238/100/100/threaded
mailing-list
Sources
- CVE List CVE-2006-6958
- NVD CVE-2006-6958
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.