# CVE-2024-0789: WP Maintenance <= 6.1.9.2 - IP Spoofing to Maintenance Mode Bypass

> Unauthenticated attackers can bypass maintenance mode by spoofing IP addresses via HTTP headers, exposing the site to the public.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-64r5-36hc-63p9

## What is CVE-2024-0789?

CVE-2024-0789 is a medium-severity vulnerability in florent73 WP Maintenance, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Maintenance plugin for WordPress is vulnerable to IP Address Spoofing in all versions up to, and including, 6.1.9.2 due to insufficient IP address validation and use of user-supplied HTTP headers as a primary method for IP retrieval. This makes it possible for unauthenticated attackers to bypass maintenance mode.

Weakness: CWE-348 (Use of Less Trusted Source)

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


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

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

## Is CVE-2024-0789 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0789 is a medium-severity vulnerability in florent73 WP Maintenance, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0789 in the wild and no public exploit code.

Affected product: florent73 WP Maintenance. 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-0789/ (Markdown: https://insights.sbomify.com/CVE-2024-0789/index.md)
```

## Sources

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

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