# CVE-2025-12822: WP Login and Register using JWT <= 3.0.0 - Missing Authorization to Authenticated (Subscriber+) API Key Exposure

> Authenticated subscribers can generate API keys to access restricted endpoints due to missing capability checks in the WP Login and Register using JWT plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 19 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-j56r-3rjm-35f7

## What is CVE-2025-12822?

CVE-2025-12822 is a medium-severity missing authorization vulnerability in cyberlord92 WP Login and Register using JWT, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-12822?


## How do I fix CVE-2025-12822?

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

## Is CVE-2025-12822 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12822 and fix it if it is affected.

What it is: CVE-2025-12822 is a medium-severity missing authorization vulnerability in cyberlord92 WP Login and Register using JWT, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12822 in the wild and no public exploit code.

Affected product: cyberlord92 WP Login and Register using JWT. 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-2025-12822/ (Markdown: https://insights.sbomify.com/CVE-2025-12822/index.md)
```

## Sources

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

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