dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-11693

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 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 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 Export WP Page to Static HTML & PDF WordPress plugin (versions up to 4.3.4) stores authentication cookies in publicly accessible cookies.txt log files. When an administrator triggers a backup, the plugin logs session cookies that can be harvested by unauthenticated attackers to impersonate administrators and gain full site access.

MitigationUpdate the plugin to the latest version immediately. If no patch is available, disable and remove the plugin. Additionally, rotate all administrator sessions and credentials as a precautionary measure since exposure of authentication cookies may have already occurred.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify if the plugin is installed
    Check the WordPress plugins directory for the 'Export WP Page to Static HTML & PDF' plugin and note its installed version number
    Affected if The plugin version is 4.3.4 or lower
  2. Search for cookies.txt log files
    Use file system search (find, grep, or similar) to locate any cookies.txt files within the web document root and subdirectories
    Affected if Any cookies.txt files exist in publicly accessible web directories
  3. Verify cookies.txt file accessibility
    Attempt to access suspected cookies.txt files via HTTP/HTTPS requests from an unauthenticated browser or curl command
    Affected if The cookies.txt files are retrievable via direct URL without authentication
  4. Inspect cookies.txt content
    Examine the contents of any found cookies.txt files for session cookie data such as authentication tokens, PHPSESSID, wordpress_logged_in cookies, or similar session identifiers
    Affected if The cookies.txt files contain active or expired session cookies from administrative users
  5. Check plugin activity logs
    Review server access logs for requests to the cookies.txt files and for plugin backup operation endpoints that may indicate the plugin was used by an administrator
    Affected if Evidence shows the backup function was executed and cookies.txt files were created and accessed

If the plugin version is 4.3.4 or lower and publicly accessible cookies.txt files containing session cookies are found, the environment is affected by this CVE.

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 plugin to the latest version immediately. If no patch is available, disable and remove the plugin. Additionally, rotate all administrator sessions and credentials as a precautionary measure since exposure of authentication cookies may have already occurred.

Recommended fix Low confidence

Latest version available on WordPress Plugin Directory (check for version > 4.3.4)

  1. Check the current version of the 'Export WP Page to Static HTML & PDF' plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate 'Export WP Page to Static HTML & PDF' and note the current version number
  4. Visit the WordPress Plugin Directory at plugins.trac.wordpress.org to check for a version newer than 4.3.4
  5. If a newer version is available, click 'Update Now' to upgrade the plugin to the latest version
  6. After updating, verify the new version number is installed
  7. Check for any cookies.txt or log files in the plugin directory and remove them if they exist

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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