dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7650

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The E2Pdf – Export Pdf Tool for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' attribute of the `e2pdf-download` shortcode in all versions up to, and including, 1.32.17. This is due to insufficient input sanitization and output escaping on the shortcode attribute. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The E2Pdf WordPress plugin fails to sanitize and escape the 'id' attribute in its e2pdf-download shortcode, allowing authenticated users with Contributor-level access or higher to inject malicious JavaScript. This stored XSS executes whenever a user accesses a page containing the crafted shortcode due to insufficient output escaping.

MitigationUpdate the E2Pdf plugin to version 1.32.18 or later when available. Until then, restrict shortcode usage to trusted users and review existing pages for suspicious e2pdf-download shortcode attributes.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify E2Pdf plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check for /wp-content/plugins/e2pdf/ directory on the server
    Affected if E2Pdf plugin is present on the WordPress site
  2. Identify the installed E2Pdf version
    In WordPress admin, click on the E2Pdf plugin to view its version number, or check the main plugin file (e.g., e2pdf.php) for the 'Version' header
    Affected if Version is below 1.32.18 (or the version cannot be determined and the plugin is active)
  3. Locate e2pdf-download shortcode usage
    Search the WordPress database or export content to find all instances of [e2pdf-download] shortcode. In MySQL: SELECT * FROM wp_posts WHERE post_content LIKE '%e2pdf-download%';
    Affected if The e2pdf-download shortcode is present in any post, page, or custom post type content
  4. Inspect shortcode id attributes for injection attempts
    Examine the id parameter in each e2pdf-download shortcode occurrence. Look for JavaScript event handlers (onload, onerror, onclick), script tags, or unusual encoded characters
    Affected if Any id attribute contains unescaped HTML, JavaScript code, or suspicious patterns that could execute in a browser
  5. Review user access controls
    Navigate to Users > All Users in WordPress admin and identify which users have Contributor, Author, Editor, or Administrator roles
    Affected if Any user with Contributor-level access or higher has the ability to create or edit content containing shortcodes

A site is affected if E2Pdf plugin is installed, the version is below 1.32.18, and users with Contributor-level access or higher can create or edit content containing the e2pdf-download shortcode.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the E2Pdf plugin to version 1.32.18 or later when available. Until then, restrict shortcode usage to trusted users and review existing pages for suspicious e2pdf-download shortcode attributes.

Recommended fix High confidence

1.32.18

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the E2Pdf – Export Pdf Tool for WordPress plugin
  4. If the plugin shows version 1.32.17 or lower, update it to version 1.32.18 or later
  5. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7650 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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