CVE-2006-1994 json
PHP remote file inclusion vulnerability in dForum 1.5 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the DF…
published 2006-04-25 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1994
- cvss
- 7.5
- 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
PHP remote file inclusion vulnerability in dForum 1.5 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the DFORUM_PATH parameter to (1) about.php, (2) admin.php, (3) anmelden.php, (4) losethread.php, (5) config.php, (6) delpost.php, (7) delthread.php, (8) dfcode.php, (9) download.php, (10) editanoc.php, (11) forum.php, (12) login.php, (13) makethread.php, (14) menu.php, (15) newthread.php, (16) openthread.php, (17) overview.php, (18) post.php, (19) suchen.php, (20) user.php, (21) userconfig.php, (22) userinfo.php, and (23) verwalten.php.
Timeline
- First public exploit (EDB-1706)
- Published
Exploit prediction
3.52% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-1706 dForum 1.5 - 'DFORUM_PATH' Multiple Remote File Inclusions webapps, 2006-04-21
- securityfocus.com http://www.securityfocus.com/bid/17650 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 |
References
-
securityfocus.com
/bid/17650
vdb-entry, exploit
-
secunia.com
/advisories/19788
third-party-advisory, vendor-advisory
-
nukedx.com
/?viewdoc=27
vendor-advisory
-
vupen.com
/english/advisories/2006/1482
vdb-entry
-
securityfocus.com
/archive/1/431758
mailing-list
-
lists.grok.org.uk
/pipermail/full-disclosure/2006-April/045369.html
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26035
vdb-entry
Sources
- CVE List CVE-2006-1994
- NVD CVE-2006-1994
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.