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

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

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

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

Herd Effects CVE-2024-3478

MEDIUM

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

2024-05-02 contact@wpscan.com

WordPress CSRF Herd Effects

6.1

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

6.1 MEDIUM

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

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

CVSS VectorVendor: wpscan

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

Low

Lifecycle Timeline

CVE Published

May 02, 2024 - 06:15 cve.org

MEDIUM 6.1

DescriptionCVE.org

AnalysisAI

The Herd Effects WordPress plugin before 5.2.7 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting effects. Rated medium severity (CVSS 6.1), this vulnerability is 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 Herd Effects WordPress plugin before 5.2.7 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting effects via CSRF attacks Affected products include: Wow-Company Herd Effects. Version information: before 5.2.7.

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.