# CVE-2025-11693: Export WP Page to Static HTML & PDF <= 4.3.4 - Unauthenticated Cookie Exposure via Log File

> Unauthenticated attackers can access exposed authentication cookies from log files, potentially leading to account takeover if an administrator triggered a backup.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-h9gx-2hf6-r5f4

## What is CVE-2025-11693?

CVE-2025-11693 is a critical vulnerability in recorp Export WordPress Pages to Static HTML & PDF — Static Site Export, published on 13 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.'

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-11693?


## How do I fix CVE-2025-11693?

No fix has been published for CVE-2025-11693 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11693 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11693 exists.

Public exploit code:

- Export WP Page to Static HTML <= 4.3.4 - Cookie Exposure (nuclei): http/cves/2025/CVE-2025-11693.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11693 and fix it if it is affected.

What it is: CVE-2025-11693 is a critical vulnerability in recorp Export WordPress Pages to Static HTML & PDF — Static Site Export, published on 13 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11693 exists.

Affected product: recorp Export WordPress Pages to Static HTML & PDF — Static Site Export. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11693/ (Markdown: https://insights.sbomify.com/CVE-2025-11693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11693
- OSV: https://osv.dev/vulnerability/CVE-2025-11693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11693/
Summaries are generated and may contain mistakes; the official description above is the record.