CVE-2009-1067 json
Cross-site scripting (XSS) vulnerability in index.php in Pixie CMS 1.01a allows remote attackers to inject arbitrary web script or HTML via…
published 2009-03-24 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1068
- cvss
- 4.3
- 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
Cross-site scripting (XSS) vulnerability in index.php in Pixie CMS 1.01a allows remote attackers to inject arbitrary web script or HTML via the x parameter.
Timeline
- First public exploit (EDB-8252)
- Published
Exploit prediction
3.69% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-8252 Pixie CMS - Cross-Site Scripting / SQL Injection webapps, 2009-03-20
- securityfocus.com http://www.securityfocus.com/bid/34189 referenced PoC, tagged "exploit" by a source, unverified
- lampsecurity.org http://lampsecurity.org/Pixie-CMS-Multiple-Vulnerabilities referenced PoC, tagged "exploit" by a source, unverified
- osvdb.org http://osvdb.org/52832 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
exploit-db.com
/exploits/8252
exploit
-
securityfocus.com
/bid/34189
vdb-entry, exploit
-
lampsecurity.org
/Pixie-CMS-Multiple-Vulnerabilities
exploit, url-repurposed
-
osvdb.org
/52832
vdb-entry, exploit
-
secunia.com
/advisories/34364
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49333
vdb-entry
-
archives.neohapsis.com
/archives/fulldisclosure/2009-03/0324.html
mailing-list
Sources
- CVE List CVE-2009-1067
- NVD CVE-2009-1067
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.