CVE-2026-32442
Missing Authorization in E2Pdf ≤1.28.15 Enables Unauthorized Access
Publication date: 2026-03-13
Last updated on: 2026-04-29
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| e2pdf | e2pdf | to 1.28.15 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'The primary mitigation step is to update the e2pdf WordPress plugin to version 1.32.00 or later, where this vulnerability is resolved.'}, {'type': 'paragraph', 'content': "If immediate updating is not possible, consider restricting access to the plugin's functions to trusted users only, although no specific workaround is detailed."}, {'type': 'paragraph', 'content': "Using services like Patchstack's auto-update feature for vulnerable plugins can also help mitigate the risk."}] [1]
Can you explain this vulnerability to me?
CVE-2026-32442 is a Broken Access Control vulnerability in the WordPress e2pdf plugin versions up to and including 1.28.15. It occurs due to missing authorization, authentication, or nonce token checks within certain functions of the plugin.
This flaw allows unprivileged users to perform actions that should be restricted to users with higher privilege levels, such as contributors or developers.
The vulnerability is classified under the OWASP Top 10 category A1: Broken Access Control.
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to perform privileged actions within the e2pdf plugin, potentially leading to unauthorized modifications or misuse of plugin functionality.
However, the CVSS severity score is relatively low (4.3 or 5 depending on the source), indicating a low priority and low impact threat.
To mitigate the risk, users should update the e2pdf plugin to version 1.32.00 or later, where the issue is resolved.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from missing authorization, authentication, or nonce token checks within certain functions of the e2pdf WordPress plugin up to version 1.28.15.
Detection would involve checking the version of the e2pdf plugin installed on your WordPress system to see if it is version 1.28.15 or earlier.
There are no specific network or system commands provided to detect exploitation attempts or presence of this vulnerability.
A practical step is to verify the plugin version via WordPress CLI with a command such as: wp plugin list | grep e2pdf
Additionally, monitoring for unauthorized actions by unprivileged users in the WordPress logs may help identify exploitation attempts, but no explicit commands or signatures are provided.