What is the CVSS score of CVE-2024-4180?

CVE-2024-4180 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 1.8%.

Is there a public PoC exploit available for CVE-2024-4180?

Yes, a public proof-of-concept exploit is available for CVE-2024-4180. Prioritise patching immediately. EPSS: 1.8%.

The Events Calendar CVE-2024-4180

CRITICAL

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

2024-06-04 contact@wpscan.com

WordPress XSS The Events Calendar

9.1

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

9.1 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Primary rating from Vendor (wpscan) · only source for this CVE.

CVSS VectorVendor: wpscan

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

CVE Published

Jun 04, 2024 - 06:15 cve.org

CRITICAL 9.1

DescriptionCVE.org

The Events Calendar WordPress plugin before 6.4.0.1 does not properly sanitize user-submitted content when rendering some views via AJAX.

AnalysisAI

The Events Calendar WordPress plugin before 6.4.0.1 does not properly sanitize user-submitted content when rendering some views via AJAX. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. 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. The Events Calendar WordPress plugin before 6.4.0.1 does not properly sanitize user-submitted content when rendering some views via AJAX. Affected products include: Stellarwp The Events Calendar. Version information: before 6.4.0.1.

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.