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

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

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

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

Logo Manager For Enamad CVE-2024-4757

HIGH

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

2024-06-25 contact@wpscan.com

WordPress XSS CSRF Logo Manager For Enamad

8.1

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

8.1 HIGH

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

CVE Published

Jun 25, 2024 - 06:15 cve.org

HIGH 8.1

DescriptionCVE.org

AnalysisAI

The Logo Manager For Enamad WordPress plugin through 0.7.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, no authentication required, 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 Logo Manager For Enamad WordPress plugin through 0.7.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack Affected products include: Wp-Master Logo Manager For Enamad. Version information: through 0.7.0.

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.