# CVE-2026-14250: Themehunk Login Registration <= 1.0.2 - Unauthenticated Privilege Escalation via 'role' Parameter

> Unauthenticated attackers can escalate privileges to editor role via the registration endpoint if public registration is enabled.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-qwpf-8g3r-53wg

## What is CVE-2026-14250?

CVE-2026-14250 is a medium-severity vulnerability in themehunk TH Login Registration, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Themehunk Login Registration plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.2. This is due to the handle_frontend_register() function in the unauthenticated /thlogin/v1/register REST endpoint accepting a user-controlled 'role' parameter and validating it only against get_editable_roles() — which returns every defined editable site role, including 'editor' — before passing it to wp_insert_user(). This makes it possible for unauthenticated attackers, when public user registration is enabled, to create new accounts with the editor role.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-14250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14250 is a medium-severity vulnerability in themehunk TH Login Registration, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14250 in the wild and no public exploit code.

Affected product: themehunk TH Login Registration. 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-14250/ (Markdown: https://insights.sbomify.com/CVE-2026-14250/index.md)
```

## Sources

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

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