CVE-2006-4559 json
Multiple PHP remote file inclusion vulnerabilities in Yet Another Community System (YACS) CMS 6.6.1 allow remote attackers to execute arbit…
published 2006-09-06 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-4547
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.6%
- EPSS 7.6% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Multiple PHP remote file inclusion vulnerabilities in Yet Another Community System (YACS) CMS 6.6.1 allow remote attackers to execute arbitrary PHP code via a URL in the context[path_to_root] parameter in (1) articles/populate.php, (2) categories/category.php, (3) categories/populate.php, (4) comments/populate.php, (5) files/file.php, (6) sections/section.php, (7) sections/populate.php, (8) tables/populate.php, (9) users/user.php, and (10) users/populate.php. The articles/article.php vector is covered by CVE-2006-4532.
Patch / fix
Timeline
- First public exploit (EDB-2282)
- Published
Exploit prediction
7.56% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-2282 YACS CMS 6.6.1 - context[path_to_root] Remote File Inclusion webapps, 2006-08-31
- secunia.com http://secunia.com/advisories/21680 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
-
yetanothercommunitysystem.com
/yacs/articles/view.php/1664
patch, url-repurposed
-
secunia.com
/advisories/21680
third-party-advisory, exploit, patch, vendor-advisory
-
osvdb.org
/31303
vdb-entry
-
osvdb.org
/31304
vdb-entry
-
osvdb.org
/31305
vdb-entry
-
osvdb.org
/31310
vdb-entry
-
osvdb.org
/31306
vdb-entry
-
osvdb.org
/31302
vdb-entry
-
osvdb.org
/31301
vdb-entry
-
osvdb.org
/31307
vdb-entry
-
osvdb.org
/31308
vdb-entry
-
osvdb.org
/31309
vdb-entry
Sources
- CVE List CVE-2006-4559
- NVD CVE-2006-4559
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.