# CVE-2026-110691: WPOrLogin < 3.1.0 - Unauthenticated Hide Login Slug Update


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-f65r-566x-cp6v

## What is CVE-2026-110691?

CVE-2026-110691 is a medium-severity vulnerability in Unknown WPOrLogin, published on 28 Oct 2026. 

### Official description

The WPOrLogin  WordPress plugin before 3.1.0 does not perform a capability check or validate a nonce before updating its hidden-login URL settings, which could allow unauthenticated attackers to reassign the login, registration and password-recovery slugs and lock the administrator out of the login interface.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110691 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110691 is a medium-severity vulnerability in Unknown WPOrLogin, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110691 in the wild and no public exploit code.

Affected product: Unknown WPOrLogin. 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-110691/ (Markdown: https://insights.sbomify.com/CVE-2026-110691/index.md)
```

## Sources

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

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