WP Encryption – One Click Free SSL Certificate & SSL / HTTPS Redirect to Force HTTPS, SSL Score <= 7.0 - Sensitive Information Exposure via insufficiently protected files
Strategic Overview
- Status
- Patched in 7.1.0
- Affected Plugin
- WP Encryption – One Click SSL / HTTPS & Free SSL Certificate, HTTPS Redirect, Security
- Affected Version
<= 7.0- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2023-7046
At a glance
CVE-2023-7046 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Encryption WordPress plugin, affecting versions <= 7.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 7.1.0; sites on affected versions should update now. Disclosed April 2024, reported by Krzysztof Zając.
Vulnerability Overview
The WP Encryption – One Click Free SSL Certificate & SSL / HTTPS Redirect to Force HTTPS, SSL Score plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.0 via exposed Private key files. This makes it possible for unauthenticated attackers to extract sensitive data including TLS Certificate Private Keys
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.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WP Encryption <= 7.0 takes a caller who can reach the endpoint. 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 WP Encryption the fix is 7.1.0: builds <= 7.0 are affected, anything from 7.1.0 onward is not.
Remediation
Update to version 7.1.0, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: WP Encryption 7.1.0 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in WP Encryption – One Click SSL / HTTPS & Free SSL Certificate, HTTPS Redirect, Security
- 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 6.1CVE-2024-13362: Freemius <= 2.10.1 Reflected DOM-Based XSS
CVE-2024-13362 - 5.4CVE-2026-3829: WP Encryption - One Click… Authenticated (Subscriber+)
CVE-2026-3829 - 4.4CVE-2026-15786: WP Encryption <= 7.8.6.6 Arbitrary File Write
CVE-2026-15786
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C