# CVE-2026-116610: The Clean Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.20.1 due to a missing capabi


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-v79r-g77x-46wf

## What is CVE-2026-116610?

CVE-2026-116610 is a medium-severity vulnerability in hornero Clean Login, published on 28 Oct 2026. 

### Official description

The Clean Login plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.20.1 due to a missing capability check on the CleanLogin_Shortcode::get_pages_with_shortcodes() function hooked to the save_post action. This makes it possible for authenticated attackers, with Contributor-level access and above, to overwrite the plugin's cl_login_url/cl_login_id/cl_register_url/cl_register_id/cl_restore_url/cl_restore_id/cl_edit_url/cl_edit_id/cl_change_password_url/cl_change_password_id options with the ID and permalink of a post they themselves authored — simply by embedding the plugin's shortcodes in their own post content.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-116610 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: hornero Clean Login. 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-116610/ (Markdown: https://insights.sbomify.com/CVE-2026-116610/index.md)
```

## Sources

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

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