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

CVE-2024-3642 has a CVSS 3.1 base score of 6.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N. EPSS exploitation probability: 0.3%.

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

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

Newsletter Popup CVE-2024-3642

MEDIUM

Cross-Site Request Forgery (CSRF) (CWE-352)

2024-05-16 contact@wpscan.com

WordPress CSRF Newsletter Popup Mndpsingh287

6.9

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

6.9 MEDIUM

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

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

CVSS VectorVendor: wpscan

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

May 16, 2024 - 06:15 cve.org

MEDIUM 6.9

DescriptionCVE.org

The Newsletter Popup WordPress plugin through 1.2 does not have CSRF check when deleting subscriber, which could allow attackers to make logged in admins perform such action via a CSRF attack

AnalysisAI

The Newsletter Popup WordPress plugin through 1.2 does not have CSRF check when deleting subscriber, which could allow attackers to make logged in admins perform such action via a CSRF attack. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Request Forgery (CSRF) (CWE-352), which allows attackers to trick authenticated users into performing unintended actions. The Newsletter Popup WordPress plugin through 1.2 does not have CSRF check when deleting subscriber, which could allow attackers to make logged in admins perform such action via a CSRF attack Affected products include: Mndpsingh287 Newsletter Popup. Version information: through 1.2.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Implement anti-CSRF tokens, validate Origin/Referer headers, use SameSite cookie attribute.