CVE-2026-12407
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 controller's 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 plugin's 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe E2Pdf WordPress plugin versions up to 1.32.26 have a Missing Authorization vulnerability in the screen_action() function. When accessed via the ?action=screen routing path, this function bypasses the nonce verification and capability checks present in index_action(). It directly uses attacker-supplied option names and values from $_POST['wp_screen_options'] in update_option() calls without any allowlist, relying only on the e2pdf_templates capability—which the plugin's UI allows administrators to grant to low-privileged roles. This enables authenticated attackers with this capability to modify arbitrary WordPress options like default_role and escalate to administrator.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check E2Pdf plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate E2Pdf, or inspect the plugin main file header for 'Version' valueAffected if Version is 1.32.26 or lower
-
Identify roles with e2pdf_templates capabilityUse a WordPress user role editor plugin or query wp_options for custom role capabilities, or inspect the plugin code for add_cap() callsAffected if Any role other than Administrator has the e2pdf_templates capability granted
-
Verify capability assignment sourceCheck if an Administrator explicitly granted e2pdf_templates to lower roles via the E2Pdf plugin's role assignment UIAffected if Non-Administrator roles were granted e2pdf_templates capability through plugin settings
-
Audit recent WordPress option changesReview wp_options table for recent modifications to sensitive options (default_role, users_can_register, admin_email) or check site logs for update_option calls via wp_screen_optionsAffected if Options were changed without Administrator knowledge or correlate with plugin activity
If E2Pdf version is 1.32.26 or lower AND any non-Administrator role holds the e2pdf_templates capability, the site is vulnerable to privilege escalation via arbitrary option modification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate to a patched version immediately. Until then, revoke the e2pdf_templates capability from all roles below Administrator using the WordPress user role editor, or disable the plugin entirely if updates are unavailable.
Plugin version newer than 1.32.26 (check WordPress plugin repository for latest stable release)
- 1. Log in to WordPress admin dashboard with administrator privileges
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'E2Pdf – Export Pdf Tool for WordPress' plugin
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. After updating, navigate to Settings > E2Pdf > Permissions
- 6. Review and restrict the 'e2pdf_templates' capability - ensure it is only granted to Administrator role
- 7. Verify the update was successful by checking the plugin version (should be newer than 1.32.26)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12407 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data