themehunk Login Registration Plugin up to 1.0.2 REST endpoint /thlogin/v1/register handle_frontend_register role name resolution

Summaryinfo

A vulnerability, which was classified as critical, was found in themehunk Login Registration Plugin up to 1.0.2. Affected is the function handle_frontend_register of the file /thlogin/v1/register of the component REST endpoint. Such manipulation of the argument role leads to name resolution. This vulnerability is documented as CVE-2026-14250. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in themehunk Login Registration Plugin up to 1.0.2 and classified as critical. Affected by this issue is the function handle_frontend_register of the file /thlogin/v1/register of the component REST endpoint. The manipulation of the argument role with an unknown input leads to a name resolution vulnerability. Using CWE to declare the problem leads to CWE-706. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at wordfence.com. This vulnerability is handled as CVE-2026-14250 since 06/30/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 07/08/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• themehunk

Name

• Login Registration Plugin

Version

• 1.0.0
• 1.0.1
• 1.0.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion