CVE-2024-5770

WP Force SSL & HTTPS SSL Redirect <= 1.66 - Missing Authorization to Settings Update

2024-06-07 00:00

Strategic Overview

Status: Patched in 1.67
Affected Plugin: WP Force SSL & HTTPS SSL Redirect
Affected Version: <= 1.66
CVSS: 4.2Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2024-5770

View all WP Force SSL & HTTPS SSL Redirect vulnerabilities

At a glance

CVE-2024-5770 is a medium-severity Missing Authorization vulnerability in the WP Force SSL & HTTPS SSL Redirect WordPress plugin, affecting versions <= 1.66. It carries a CVSS score of 4.2 (reachable over the network). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.67; sites on affected versions should update now. Disclosed June 2024, reported by Foxyyy.

Vulnerability Overview

The WP Force SSL & HTTPS SSL Redirect plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'ajax_save_setting' function in versions up to, and including, 1.66. This makes it possible for authenticated attackers, subscriber-level permissions and above, to update the plugin settings.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-862: Missing Authorization

WP Force SSL & HTTPS SSL Redirect <= 1.66 carries this weakness at ajax_save_setting, and reaching it 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. For WP Force SSL & HTTPS SSL Redirect the fix is 1.67: builds <= 1.66 are affected, anything from 1.67 onward is not.

Remediation

Update to version 1.67, or a newer patched version

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. None of that substitutes for the fix: WP Force SSL & HTTPS SSL Redirect 1.67 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-5770 https://www.wordfence.com/threat-intel/vulnerabilities/id/c2081e4a-c6b7-4730-be59-bc728b90ecaa https://nvd.nist.gov/vuln/detail/CVE-2024-5770

CVSS Vector

4.2

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L

Base

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityLow

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/