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

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

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

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

Counter Box CVE-2024-3481

MEDIUM

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

2024-05-02 contact@wpscan.com

WordPress CSRF Counter Box

5.2

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

5.2 MEDIUM

AV:N/AC:L/PR:H/UI:R/S:U/C:L/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:H/UI:R/S:U/C:L/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

High

Availability

None

Lifecycle Timeline

CVE Published

May 02, 2024 - 06:15 cve.org

MEDIUM 5.2

DescriptionCVE.org

AnalysisAI

The Counter Box WordPress plugin before 1.2.4 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such deleting counters via. Rated medium severity (CVSS 5.2), 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 Counter Box WordPress plugin before 1.2.4 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such deleting counters via CSRF attacks Affected products include: Wow-Company Counter Box. Version information: before 1.2.4.

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.