Subscriber-level API key exposure via missing capability check
Published Nov 19, 2025 · Updated Nov 19, 2025
Missing authorization in miniOrange WP Login and Register using JWT 3.0.0 and earlier allows remote authenticated users to obtain an API key. The mo_jwt_generate_new_api_key function generates and returns a new API key without checking the caller’s WordPress capability. Subscriber-level access is sufficient when the site has no API key configured, and the new key grants access to restricted REST endpoints.
Summary
What happened
Missing authorization in miniOrange WP Login and Register using JWT 3.0.0 and earlier allows remote authenticated users to obtain an API key. The mo_jwt_generate_new_api_key function generates and returns a new API key without checking the caller’s WordPress capability. Subscriber-level access is sufficient when the site has no API key configured, and the new key grants access to restricted REST endpoints.
The record
- CVE
- CVE-2025-12822
- Published
- Nov 19, 2025
- Updated
- Nov 19, 2025
- Vendor
- miniOrange
- Product
- WP Login and Register using JWT
- Classifications
- CWE-862, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 2025CVE publishedPublication date reported by the CVE source.
- Nov 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=3.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo