What is the CVSS score of CVE-2012-4469?

CVE-2012-4469 has a CVSS 2.0 base score of 2.6 (Low). CVSS vector: AV:N/AC:H/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.4%.

Is there a patch available for CVE-2012-4469?

Yes, a patch is available for CVE-2012-4469. Update the affected software to the latest version immediately.

Hashcash CVE-2012-4469

LOW

Cross-site Scripting (XSS) (CWE-79)

2012-11-30 secalert@redhat.com

XSS Hashcash

2.6

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.6 LOW

AV:N/AC:H/Au:N/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:H/Au:N/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

High

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Nov 30, 2012 - 22:55 cve.org

LOW 2.6

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in the Hashcash module 6.x-2.x before 6.x-2.6 and 7.x-2.x before 7.x-2.2 for Drupal, when "Log failed hashcash" is enabled, allows remote attackers to inject arbitrary web script or HTML via an invalid token, which is not properly handled when administrators use the Database logging module.

AnalysisAI

Cross-site scripting (XSS) vulnerability in the Hashcash module 6.x-2.x before 6.x-2.6 and 7.x-2.x before 7.x-2.2 for Drupal, when "Log failed hashcash" is enabled, allows remote attackers to inject. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Cross-site scripting (XSS) vulnerability in the Hashcash module 6.x-2.x before 6.x-2.6 and 7.x-2.x before 7.x-2.2 for Drupal, when "Log failed hashcash" is enabled, allows remote attackers to inject arbitrary web script or HTML via an invalid token, which is not properly handled when administrators use the Database logging module. Affected products include: Simon Rycroft Hashcash. Version information: before 6..

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.