WordPress HTTPS (SSL) <= 3.4.0 - Missing Authorization to Settings Change
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WordPress HTTPS (SSL)
- Affected Version
<= 3.4.0- CVSS
- 7.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the WordPress HTTPS (SSL) WordPress plugin, affecting versions <= 3.4.0. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high availability impact). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2022.
Vulnerability Overview
The WordPress HTTPS (SSL) plugin is vulnerable to authenticated settings change in versions up to, and including, 3.4.0 due to using a nonce check in place of a capability check. This allows authenticated users with contributor permissions and above to modify the plugin settings, which can be used to configure the site such that it is not accessible.
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 interaction from a victim user. A successful exploit has high impact on availability.
CWE-862: Missing Authorization
Reaching this weakness in WordPress HTTPS (SSL) <= 3.4.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for WordPress HTTPS (SSL) yet, so installs running <= 3.4.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C