CVE-2025-11693

Export WP Page to Static HTML & PDF <= 4.3.4 - Unauthenticated Cookie Exposure via Log File

2025-12-12 15:39
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 5.0.0
Affected Version
<= 4.3.4
CVSS
9.8Critical
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-11693
View all Export WordPress Pages to Static HTML & PDF — Static Site Export vulnerabilities

At a glance

CVE-2025-11693 is a critical-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Export WordPress Pages to Static HTML & PDF WordPress plugin, affecting versions <= 4.3.4. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.0.0; sites on affected versions should update now. Disclosed December 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

The Export WP Page to Static HTML & PDF plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.3.4 through publicly exposed cookies.txt files containing authentication cookies. This makes it possible for unauthenticated attackers to cookies that may have been injected into the log file if the site administrator triggered a back-up using a specific user role like 'administrator.'

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, 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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Export WordPress Pages to Static HTML & PDF <= 4.3.4 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Export WordPress Pages to Static HTML & PDF the fix is 5.0.0: builds <= 4.3.4 are affected, anything from 5.0.0 onward is not.

Remediation

Update to version 5.0.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Export WordPress Pages to Static HTML & PDF 5.0.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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