What is the CVSS score of CVE-2022-0535?

CVE-2022-0535 has a CVSS 3.1 base score of 4.8 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 1.3%.

Is there a public PoC exploit available for CVE-2022-0535?

Yes, a public proof-of-concept exploit is available for CVE-2022-0535. Prioritise patching immediately. EPSS: 1.3%.

Is there a patch available for CVE-2022-0535?

Yes, a patch is available for CVE-2022-0535. Update the affected software to the latest version immediately.

E2pdf CVE-2022-0535

MEDIUM

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

2022-03-07 contact@wpscan.com

XSS WordPress E2pdf

4.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.8 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Mar 07, 2022 - 09:15 nvd

MEDIUM 4.8

DescriptionNVD

The E2Pdf WordPress plugin before 1.16.45 does not sanitise and escape some of its settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed

AnalysisAI

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 E2Pdf WordPress plugin before 1.16.45 does not sanitise and escape some of its settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed Affected products include: E2Pdf. Version information: before 1.16.45.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.