WP Login and Register using JWT <= 3.0.0 - Missing Authorization to Authenticated (Subscriber+) API Key Exposure
Strategic Overview
- Status
- Patched in 3.1.0
- Affected Plugin
- WP Login and Register using JWT
- Affected Version
<= 3.0.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-12822
At a glance
CVE-2025-12822 is a medium-severity Missing Authorization vulnerability in the WP Login and Register using JWT WordPress plugin, affecting versions <= 3.0.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.1.0; sites on affected versions should update now. Disclosed November 2025, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
The WP Login and Register using JWT plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'mo_jwt_generate_new_api_key' function in all versions up to, and including, 3.0.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to generate a new API key on site's that do not have an API key configured and subsequently use that to access restricted endpoints.
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-862: Missing Authorization
WP Login and Register using JWT <= 3.0.0 carries this weakness at mo_jwt_generate_new_api_key, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Login and Register using JWT the fix is 3.1.0: builds <= 3.0.0 are affected, anything from 3.1.0 onward is not.
Remediation
Update to version 3.1.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Login and Register using JWT 3.1.0 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