CVE-2026-125764 in e2pdf Plugin
Summary
by MITRE • 11/15/2026
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in E2Pdf.com e2pdf e2pdf allows Stored XSS.This issue affects e2pdf: from n/a through 1.32.65.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/15/2026
The identified vulnerability represents a classic instance of Improper Neutralization of Input During Web Page Generation, commonly known as Cross-Site Scripting or XSS. Specifically, this is classified as a Stored XSS flaw within the e2pdf application developed by E2Pdf.com. Unlike reflected XSS attacks where malicious scripts are delivered via immediate user interaction such as clicking a crafted link, stored vulnerabilities persist on the target server's database or file system. This means that once an attacker successfully injects their payload, it is saved and subsequently served to every other user who views the affected content. The vulnerability affects versions of e2pdf ranging from its initial release up through version 1.32.65, indicating a long-standing exposure window for users operating within this version range without appropriate patches or mitigations in place.
From a technical perspective, the core flaw lies in the application's failure to properly sanitize or encode user-supplied input before rendering it into HTML output. When a user submits data through an e2pdf feature that allows file uploads, metadata entry, or document annotation, the system accepts this input without adequate validation against executable script tags or event handlers. Consequently, when another user accesses the affected PDF document or associated page within the application's interface, the browser interprets the injected code as legitimate content rather than data. This execution context grants the attacker the ability to run arbitrary JavaScript in the victim's browser session, leveraging the trust that users typically place in the e2pdf platform and their own authenticated sessions.
The operational impact of this vulnerability is severe due to its persistent nature. An attacker can exploit this flaw to steal sensitive information such as session cookies, authentication tokens, or personally identifiable information stored within local storage if accessible via script. Furthermore, it enables account takeover scenarios where the attacker hijacks a victim's active session by exfiltrating credentials or performing actions on behalf of the user without their knowledge. Beyond data theft, this vulnerability can be used to deface web pages, redirect users to malicious phishing sites designed to harvest additional credentials, or deploy further malware through drive-by downloads if combined with other browser-specific exploits. The persistence of the payload ensures that multiple victims are compromised over time, amplifying the potential damage significantly compared to transient attack vectors.
In terms of industry standard classifications, this vulnerability aligns directly with CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). More specifically, it falls under the sub-category of Stored Cross-Site Scripting (CWE-80). Within the MITRE ATT&CK framework, this behavior maps to T1059.007: JavaScript and potentially T1204.002: Malicious File, depending on how the payload is delivered and executed. The attack vector typically involves Initial Access through user interaction or exploitation of a vulnerability in an application component, followed by Execution within the victim's browser environment to achieve persistence or privilege escalation relative to the web application context.
To mitigate this risk, developers must implement strict input validation and output encoding strategies. All user-supplied data should be validated against a whitelist of allowed characters before processing, ensuring that only expected formats are accepted. More critically, when rendering content back to the browser, all special HTML characters such as ampersands, less-than signs, greater-than signs, quotes, and apostrophes must be encoded using context-aware output encoding techniques appropriate for HTML body contexts. Implementing a Content Security Policy (CSP) header can also significantly reduce the impact by restricting the sources from which scripts are allowed to load or execute, thereby preventing inline script execution even if injection occurs. Additionally, setting HttpOnly flags on session cookies prevents JavaScript access to these tokens, limiting the scope of potential data theft in the event of a successful XSS attack. Users should upgrade to patched versions of e2pdf immediately and administrators should review recent uploads for any suspicious content that may have been injected during the vulnerable period.