CVE-2026-12407

NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-12407
CWE	https://cwe.mitre.org/data/definitions/862.html

The E2Pdf – Export Pdf Tool for WordPress plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.32.26. This is due to the screen_action() function lacking a dedicated capability check and nonce verification — when invoked via the ?action=screen routing path the controllers index_action() nonce gate is bypassed entirely — while reading an attacker-controlled option name and value from $_POST[wp_screen_options] and passing them directly to update_option() with no allowlist, relying solely on the page-level e2pdf_templates capability which the plugins own Permissions UI allows administrators to grant to any role including Subscriber, Contributor, Author, or Editor. This makes it possible for authenticated attackers, with a custom role that has been granted the e2pdf_templates capability, to overwrite arbitrary WordPress options such as default_role and thereby escalate their privileges to administrator.

Weakness

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Potential Mitigations

Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

https://cwe.mitre.org/data/definitions/665.html

Missing Authorization

Weakness

Potential Mitigations

Related Attack Patterns

References