Themehunk Login Registration <= 1.0.2 - Unauthenticated Privilege Escalation via 'role' Parameter
Strategic Overview
- Status
- Patched in 1.0.3
- Affected Plugin
- TH Login Registration
- Affected Version
<= 1.0.2- CVSS
- 6.3Medium
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-14250
At a glance
CVE-2026-14250 is a medium-severity Improper Privilege Management vulnerability in the TH Login Registration WordPress plugin, affecting versions <= 1.0.2. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.3; sites on affected versions should update now. Disclosed July 2026, reported by Chi Trung Huynh.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-269: Improper Privilege Management
TH Login Registration <= 1.0.2 carries this weakness at role, and reaching it takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For TH Login Registration the fix is 1.0.3: builds <= 1.0.2 are affected, anything from 1.0.3 onward is not.
Remediation
Update to version 1.0.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: TH Login Registration 1.0.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C