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

CVE-2012-5559 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.2%.

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

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

Ctools CVE-2012-5559

LOW

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

2012-12-03 secalert@redhat.com

XSS Ctools

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

Dec 03, 2012 - 21:55 cve.org

LOW 2.6

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in the page manager node view task in the Chaos tool suite (ctools) module 6.x-1.x before 6.x-1.10 for Drupal allows remote authenticated users with permissions to submit or edit nodes to inject arbitrary web script or HTML via the page title.

AnalysisAI

Cross-site scripting (XSS) vulnerability in the page manager node view task in the Chaos tool suite (ctools) module 6.x-1.x before 6.x-1.10 for Drupal allows remote authenticated users with. 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 page manager node view task in the Chaos tool suite (ctools) module 6.x-1.x before 6.x-1.10 for Drupal allows remote authenticated users with permissions to submit or edit nodes to inject arbitrary web script or HTML via the page title. Affected products include: Chaos Tool Suite Project Ctools. 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.