CVE-2009-3760 json
Static code injection vulnerability in config/writeconfig.php in the sample code in the XenServer Resource Kit in Citrix XenCenterWeb allow…
published 2009-10-22 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3732
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 1
- Exploit-DB
Summary
Static code injection vulnerability in config/writeconfig.php in the sample code in the XenServer Resource Kit in Citrix XenCenterWeb allows remote attackers to inject arbitrary PHP code into include/config.ini.php via the pool1 parameter. NOTE: some of these details are obtained from third party information.
Timeline
- First public exploit (EDB-9106)
- Published
Exploit prediction
2.73% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-9106 citrix xencenterweb - Cross-Site Scripting / SQL Injection / Remote Code Execution remote, 2009-07-10
- securityfocus.com http://www.securityfocus.com/archive/1/504764 referenced PoC, tagged "exploit" by a source, unverified
- securenetwork.it http://securenetwork.it/ricerca/advisory/download/SN-2009-01.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/35592 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
-
exploit-db.com
/exploits/9106
exploit
-
securityfocus.com
/archive/1/504764
mailing-list, exploit
-
securenetwork.it
/ricerca/advisory/download/SN-2009-01.txt
exploit
-
securityfocus.com
/bid/35592
vdb-entry, exploit
-
vupen.com
/english/advisories/2009/1814
vdb-entry, vendor-advisory
-
securitytracker.com
/id?1022520
vdb-entry
Sources
- CVE List CVE-2009-3760
- NVD CVE-2009-3760
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.