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

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

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

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

Contact Forms CVE-2012-2071

LOW

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

2012-08-14 secalert@redhat.com

XSS Contact Forms

2.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Aug 14, 2012 - 23:55 cve.org

LOW 2.1

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in the Contact Forms module 6.x-1.x before 6.x-1.13 for Drupal when the core contact form is enabled, allows remote authenticated users with the administer site-wide contact form permission to inject arbitrary web script or HTML via unspecified vectors.

AnalysisAI

Cross-site scripting (XSS) vulnerability in the Contact Forms module 6.x-1.x before 6.x-1.13 for Drupal when the core contact form is enabled, allows remote authenticated users with the administer. Rated low severity (CVSS 2.1), 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 Contact Forms module 6.x-1.x before 6.x-1.13 for Drupal when the core contact form is enabled, allows remote authenticated users with the administer site-wide contact form permission to inject arbitrary web script or HTML via unspecified vectors. Affected products include: Geoff Davies Contact Forms. 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.