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

CVE-2012-0933 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: 2.1%.

Is there a public PoC exploit available for CVE-2012-0933?

Yes, a public proof-of-concept exploit is available for CVE-2012-0933. Prioritise patching immediately. EPSS: 2.1%.

Acidcat Cms CVE-2012-0933

LOW

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

2012-01-29 cve@mitre.org

XSS Acidcat Cms

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

Jan 29, 2012 - 04:04 cve.org

LOW 2.6

DescriptionCVE.org

Multiple cross-site scripting (XSS) vulnerabilities in Acidcat CMS 3.5.1, 3.5.2, 3.5.6, and possibly earlier allow remote attackers to inject arbitrary web script or HTML via the PATH_INFO to (1) admin_colors.asp, (2) admin_config.asp, and (3) admin_cat_add.asp in admin/.

AnalysisAI

Multiple cross-site scripting (XSS) vulnerabilities in Acidcat CMS 3.5.1, 3.5.2, 3.5.6, and possibly earlier allow remote attackers to inject arbitrary web script or HTML via the PATH_INFO to (1). Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.

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. Multiple cross-site scripting (XSS) vulnerabilities in Acidcat CMS 3.5.1, 3.5.2, 3.5.6, and possibly earlier allow remote attackers to inject arbitrary web script or HTML via the PATH_INFO to (1) admin_colors.asp, (2) admin_config.asp, and (3) admin_cat_add.asp in admin/. Affected products include: Acidcat Acidcat Cms.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.