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

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

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

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

Pz Linkcard CVE-2024-0672

HIGH

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

2024-03-28 contact@wpscan.com

WordPress XSS Pz Linkcard

7.1

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

7.1 HIGH

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

CVE Published

Mar 28, 2024 - 05:15 cve.org

HIGH 7.1

DescriptionCVE.org

AnalysisAI

The Pz-LinkCard WordPress plugin through 2.5.1 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. Rated high severity (CVSS 7.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 Pz-LinkCard WordPress plugin through 2.5.1 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: Popozure Pz-Linkcard. Version information: through 2.5.1.

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.