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

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

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

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

Hl Twitter CVE-2024-3629

LOW

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

2024-05-15 contact@wpscan.com

WordPress CSRF Hl Twitter

2.4

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

2.4 LOW

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

May 15, 2024 - 06:15 cve.org

LOW 2.4

DescriptionCVE.org

The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

AnalysisAI

The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack. Rated low severity (CVSS 2.4), 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 HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack Affected products include: Dachande663 Hl Twitter. Version information: through 2014.1.18.

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.