# CVE-2026-86796: Security feature bypass in Hide My WP Ghost

> Unauthenticated attackers can bypass firewall and URL hiding protections by spoofing WooCommerce request parameters, exposing concealed admin URLs.

- **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:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-5vw4-phcp-qmr8

## What is CVE-2026-86796?

CVE-2026-86796 is a medium-severity vulnerability in Unknown Hide My WP Ghost, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Hide My WP Ghost WordPress plugin before 7.0.11 does not verify that a request is a genuine WooCommerce request before disabling its firewall, threat-detection and login/URL-hiding protections, treating the mere presence of an attacker-suppliable request parameter as sufficient, which allows unauthenticated attackers to disable those protections and re-expose the concealed login and admin URLs on any request.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2026-86796?


## How do I fix CVE-2026-86796?

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

## Is CVE-2026-86796 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86796 and fix it if it is affected.

What it is: CVE-2026-86796 is a medium-severity vulnerability in Unknown Hide My WP Ghost, published on 18 Sep 2026. 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-2026-86796 in the wild and no public exploit code.

Affected product: Unknown Hide My WP Ghost. 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-2026-86796/ (Markdown: https://insights.sbomify.com/CVE-2026-86796/index.md)
```

## Sources

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

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