CVE-2006-2395 json
PHP remote file inclusion vulnerability in resources/includes/popp.config.loader.inc.php in PopSoft Digital PopPhoto Studio 3.5.4 and earli…
published 2006-05-16 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2396
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
PHP remote file inclusion vulnerability in resources/includes/popp.config.loader.inc.php in PopSoft Digital PopPhoto Studio 3.5.4 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the include_path parameter (cfg['popphoto_base_path'] variable). NOTE: Pixaria has notified CVE that "PopPhoto is NOT a product of Pixaria. It was a product of PopSoft Digital and is only hosted by Pixaria as a courtesy... The vulnerability listed was patched by the previous vendor and all previous users have received this update."
Timeline
- First public exploit (EDB-27868)
- Published
Exploit prediction
3.67% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27868 Pixaria PopPhoto 3.5.4 - 'CFG[popphoto_base_path]' Remote File Inclusion webapps, 2006-05-15
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
vupen.com
/english/advisories/2006/1792
vdb-entry, vendor-advisory
-
secunia.com
/advisories/20087
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/17970
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26449
vdb-entry
-
attrition.org
/pipermail/vim/2006-June/000869.html
mailing-list
-
securitytracker.com
/id?1016092
vdb-entry
-
pixaria.com
/news/article/35/
url-repurposed
-
osvdb.org
/25524
vdb-entry
- pridels0.blogspot.com /2006/05/popphoto-remote-file-inclusion-vuln.html
Sources
- CVE List CVE-2006-2395
- NVD CVE-2006-2395
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.