# CVE-2024-5770: WP Force SSL & HTTPS SSL Redirect <= 1.66 - Missing Authorization to Settings Update

> Authenticated subscribers can modify plugin settings due to missing capability checks in WP Force SSL & HTTPS SSL Redirect.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-94j4-8q96-67wx

## What is CVE-2024-5770?

CVE-2024-5770 is a medium-severity missing authorization vulnerability in webfactory WP Force SSL & HTTPS SSL Redirect, published on 8 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-5770?

It affects 1 product.


Products: Webfactoryltd Wp Force Ssl.

## How do I fix CVE-2024-5770?

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

## Is CVE-2024-5770 being exploited?

There is no known exploitation of CVE-2024-5770 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5770 and fix it if it is affected.

What it is: CVE-2024-5770 is a medium-severity missing authorization vulnerability in webfactory WP Force SSL & HTTPS SSL Redirect, published on 8 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5770 in the wild and no public exploit code.

Affected product: webfactory WP Force SSL & HTTPS SSL Redirect. 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-2024-5770/ (Markdown: https://insights.sbomify.com/CVE-2024-5770/index.md)
```

## Sources

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

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