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

CVE-2012-4496 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-4496?

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

Custom Pub CVE-2012-4496

LOW

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

2012-10-31 secalert@redhat.com

XSS Custom Pub

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

Oct 31, 2012 - 16:55 cve.org

LOW 2.1

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in the Custom Publishing Options module 6.x-1.x before 6.x-1.4 for Drupal allows remote authenticated users with the "administer nodes" permission to inject arbitrary web script or HTML via the status labels parameter.

AnalysisAI

Cross-site scripting (XSS) vulnerability in the Custom Publishing Options module 6.x-1.x before 6.x-1.4 for Drupal allows remote authenticated users with the "administer nodes" permission to inject. 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 Custom Publishing Options module 6.x-1.x before 6.x-1.4 for Drupal allows remote authenticated users with the "administer nodes" permission to inject arbitrary web script or HTML via the status labels parameter. Affected products include: Inclind Custom Pub. 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.