dbcve.org
E2pdfWordPress extension

CVE-2024-43318

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-18
Fix available
A fix is available. Upgrade to 1.25.11 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in E2Pdf e2pdf e2pdf.This issue affects e2pdf: from n/a through <= 1.25.05.

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 · moderate confidence

Cross-site scripting (XSS) vulnerability in the E2Pdf WordPress plugin allows attackers to inject malicious scripts through unsanitized input that gets rendered in web pages, potentially compromising other users' sessions or performing actions on their behalf.

MitigationUpdate E2Pdf plugin to the latest patched version, or implement proper input sanitization and output encoding on affected input fields before the fix is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
E2pdfWordPress extension
Affected:< 1.25.11

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Check E2Pdf plugin version via WordPress admin
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate E2Pdf in the list and read the version number displayed below the plugin name
    Affected if The displayed version number is lower than 1.25.11 (for example, 1.25.10 or earlier)
  2. Verify E2Pdf plugin version in plugin files
    Access the WordPress site via FTP or file manager, navigate to /wp-content/plugins/e2pdf/ folder, open the main plugin file (typically e2pdf.php or index.php) and locate the version constant in the plugin header comments
    Affected if The version defined in the file header is less than 1.25.11
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that E2Pdf shows as 'Active' rather than 'Inactive' or 'Network Active'
    Affected if The plugin is currently active and the version is below 1.25.11
  4. Check version via WP-CLI if available
    Run command 'wp plugin list --name=e2pdf' on the server command line to retrieve the current version status
    Affected if The returned version value is less than 1.25.11 and status shows as 'active'

Your environment is affected if you have an active installation of the E2Pdf WordPress plugin with version 1.25.10 or earlier.

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
Upgrade available Upgrade to 1.25.11 or later
Fixed in 1.25.11
Interim mitigation

Update E2Pdf plugin to the latest patched version, or implement proper input sanitization and output encoding on affected input fields before the fix is applied.

Recommended fix High confidence

1.25.11 or later

  1. 1. Back up your WordPress site before performing any updates
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the E2Pdf plugin in the list
  5. 5. If an update is available, click 'Update Now' to update to the latest version (1.25.11 or later)
  6. 6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  7. 7. Verify the plugin version after updating to confirm the fix is applied

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

Fix this in E2pdf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43318 — 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-2024-43318 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