CVE-2008-6533 json
Drupal 5.x before 5.13 and 6.x before 6.7 does not delete all related content when an input format is deleted, which prevents the content from being properly filtered and allows remote attackers to conduct cross-site scripting (XSS) attacks via unspecified vectors.
published 17y ago modified 5mo ago also EUVD-2008-6500
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Drupal 5.x before 5.13 and 6.x before 6.7 does not delete all related content when an input format is deleted, which prevents the content from being properly filtered and allows remote attackers to conduct cross-site scripting (XSS) attacks via unspecified vectors.
Patch / fix
- drupal.org/node/345441 advisory
Is CVE-2008-6533 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.01% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-18).
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
- Technology feeds
References
-
drupal.org
/node/345441
patch, vendor-advisory
-
redhat.com
/archives/fedora-package-announce/2008-December/msg00767.html
vendor-advisory
-
redhat.com
/archives/fedora-package-announce/2008-December/msg00740.html
vendor-advisory
-
secunia.com
/advisories/33112
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2008/3414
vdb-entry
-
secunia.com
/advisories/33147
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/47259
vdb-entry
-
osvdb.org
/50662
vdb-entry
Sources
- CVE List CVE-2008-6533
- NVD CVE-2008-6533
Fencer Intel 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.