CVE-2009-0817 json
Cross-site scripting (XSS) vulnerability in the Protected Node module 5.x before 5.x-1.4 and 6.x before 6.x-1.5, a module for Drupal, allow…
published 2009-03-05 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0814
- cvss
- 3.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in the Protected Node module 5.x before 5.x-1.4 and 6.x before 6.x-1.5, a module for Drupal, allows remote authenticated users with "administer site configuration" permissions to inject arbitrary web script or HTML via the Password page info field, which is not properly handled by the protected_node_enterpassword function in protected_node.module.
Patch / fix
- vupen.com/english/advisories/2009/0572 advisory
- drupal.org/node/386606 advisory
- drupal.org/node/386604 advisory
Exploit prediction
1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- drupal.org http://drupal.org/node/385950 referenced PoC, tagged "exploit" by a source, unverified
- lampsecurity.org http://lampsecurity.org/node/28 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
vupen.com
/english/advisories/2009/0572
vdb-entry, patch, vendor-advisory
-
drupal.org
/node/386606
patch, vendor-advisory
-
drupal.org
/node/386604
patch, vendor-advisory
-
drupal.org
/node/385950
exploit, vendor-advisory
-
lampsecurity.org
/node/28
exploit, url-repurposed
-
secunia.com
/advisories/34060
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/48980
vdb-entry
-
osvdb.org
/52300
vdb-entry
Sources
- CVE List CVE-2009-0817
- NVD CVE-2009-0817
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.