CVE-2026-66710

E2Pdf – Export Pdf Tool for WordPress <= 1.32.40 - Unauthenticated Local File Inclusion

2026-08-05 00:00
Noman Riffat

Strategic Overview

Status
Patched in 1.32.43
Affected Plugin
E2Pdf – Export Pdf Tool for WordPress
Affected Version
<= 1.32.40
CVSS
8.1High
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2026-66710
View all E2Pdf – Export Pdf Tool for WordPress vulnerabilities

At a glance

CVE-2026-66710 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the E2Pdf WordPress plugin, affecting versions <= 1.32.40. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.32.43; sites on affected versions should update now. Disclosed August 2026, reported by Noman Riffat.

Vulnerability Overview

The E2Pdf – Export Pdf Tool for WordPress plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 1.32.40. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other "safe" file types can be uploaded and included.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

E2Pdf <= 1.32.40 carries this weakness at safe, and reaching it takes no account at all. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For E2Pdf the fix is 1.32.43: builds <= 1.32.40 are affected, anything from 1.32.43 onward is not.

Remediation

Update to version 1.32.43, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: E2Pdf 1.32.43 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-66710https://www.wordfence.com/threat-intel/vulnerabilities/id/6d7a4f08-1a6a-4bc3-b09c-ad5fc7c5d1a7https://nvd.nist.gov/vuln/detail/CVE-2026-66710

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C