What is the CVSS score of EUVD-2026-33656?

EUVD-2026-33656 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.0%.

Which versions of e2pdf WordPress Plugin are affected by EUVD-2026-33656?

The e2pdf WordPress plugin (versions ≤1.32.14) contains a reflected cross-site scripting vulnerability accessible to unauthenticated attackers, with no public exploit identified at time of analysis.

How to fix or mitigate EUVD-2026-33656?

Within 24 hours: Audit WordPress environments for e2pdf plugin versions ≤1.32.14 and disable the plugin if not mission-critical; deploy Web Application Firewall (WAF) rules to block reflected XSS payloads. Within 7 days: Contact vendor to confirm security update timeline, document all affected installations, and implement Content Security Policy (CSP) headers restricting inline script execution. Within 30 days: Monitor application and WAF logs for exploitation signatures, conduct staff security awareness training on malicious link vectors, and establish contingency plan for plugin replacement or vendor patch deployment when available.

e2pdf WordPress Plugin EUVD-2026-33656

| CVE-2026-42681 HIGH

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

2026-06-01 audit@patchstack.com

GHSA-3v6w-rf9f-2qhg

WordPress XSS Wordpress Plugin

7.1

CVSS 3.1 · Vendor: patchstack

Severity by source

Vendor (patchstack) PRIMARY

7.1 HIGH

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

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

CVSS VectorVendor: patchstack

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

Analysis Generated

Jun 01, 2026 - 15:33 vuln.today

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in E2Pdf.Com e2pdf allows Reflected XSS.

This issue affects e2pdf: from n/a through 1.32.14.

AnalysisAI

Reflected cross-site scripting in the e2pdf WordPress plugin (versions up to and including 1.32.14) allows unauthenticated remote attackers to execute arbitrary JavaScript in a victim's browser after the victim clicks a crafted link. The flaw stems from improper neutralization of user input during web page generation (CWE-79) and carries a CVSS 3.1 score of 7.1 with a scope change. No public exploit identified at time of analysis and the issue is not listed in CISA KEV.

Technical ContextAI

e2pdf (by E2Pdf.Com) is a WordPress plugin that generates PDF documents from WordPress posts, pages, and form data. The vulnerability is a classic CWE-79 (Improper Neutralization of Input During Web Page Generation) reflected XSS, meaning user-supplied input is returned in an HTTP response without proper output encoding or sanitization, enabling the browser to interpret attacker-controlled data as executable script. The CVSS scope change (S:C) suggests the injected script can affect resources beyond the vulnerable component - typical for XSS where script executes in the browser security context of the WordPress site and can reach other origins, cookies, or admin functionality. The Patchstack advisory (the sole reference) categorizes this within the WordPress plugin ecosystem.

RemediationAI

No vendor-released patch version was identified in the provided input data - the Patchstack advisory references version 1.32.14 as the last known vulnerable release but no fixed version is cited. Site operators should consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/e2pdf/vulnerability/wordpress-e2pdf-plugin-1-32-14-reflected-cross-site-scripting-xss-vulnerability for an updated fix version and upgrade as soon as one is published. As compensating controls until a patch is available, administrators can deactivate the e2pdf plugin (side effect: PDF generation functionality is lost), deploy a web application firewall rule that blocks script-like payloads on e2pdf endpoints (side effect: may false-positive on legitimate document content), or enforce a strict Content-Security-Policy header that disallows inline scripts on WordPress admin pages (side effect: may break other plugins that rely on inline JavaScript).