| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Drupal up to 4.7.3 and classified as problematic. Impacted is an unknown function of the component XML Parser. This manipulation causes cross site scripting. This vulnerability is tracked as CVE-2006-5475. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.
Details
A vulnerability has been found in Drupal up to 4.7.3 (Content Management System) and classified as problematic. Affected by this vulnerability is an unknown part of the component XML Parser. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Multiple cross-site scripting (XSS) vulnerabilities in the XML parser in Drupal 4.6.x before 4.6.10 and 4.7.x before 4.7.4 allow remote attackers to inject arbitrary web script or HTML via a crafted RSS feed.
The weakness was disclosed 10/18/2006 by Erdem Köse (Website). The advisory is shared at secunia.com. This vulnerability is known as CVE-2006-5475 since 10/24/2006. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
It is declared as proof-of-concept.
Upgrading to version 4.6.x eliminates this vulnerability.
The vulnerability is also documented in the databases at OSVDB (29922†) and Secunia (SA22486†). The entries VDB-32919 and VDB-32918 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://www.drupal.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Drupal 4.6.x
Timeline
10/18/2006 🔍10/20/2006 🔍
10/24/2006 🔍
10/24/2006 🔍
03/12/2015 🔍
04/25/2026 🔍
Sources
Product: drupal.orgAdvisory: secunia.com⛔
Researcher: Erdem Köse
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-5475 (🔍)
GCVE (CVE): GCVE-0-2006-5475
GCVE (VulDB): GCVE-100-32917
Secunia: 22486
OSVDB: 29922 - Drupal XML Parser RSS Feed XSS
Vupen: ADV-2006-4120
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 04/25/2026 07:35
Changes: 03/12/2015 22:21 (55), 08/06/2018 07:31 (1), 04/25/2026 07:35 (19)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.