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

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

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

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

Web Directory Free CVE-2024-3669

MEDIUM

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

2024-07-30 contact@wpscan.com

WordPress XSS Web Directory Free

6.8

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

6.8 MEDIUM

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

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

CVSS VectorVendor: wpscan

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

Low

Lifecycle Timeline

CVE Published

Jul 30, 2024 - 06:15 cve.org

MEDIUM 6.8

DescriptionCVE.org

AnalysisAI

The Web Directory Free WordPress plugin before 1.7.2 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used. Rated medium severity (CVSS 6.8), 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 Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. The Web Directory Free WordPress plugin before 1.7.2 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin Affected products include: Salephpscripts Web Directory Free. Version information: before 1.7.2.

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.