Quick answers
- Is CVE-2026-89027 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89027 being exploited in the wild.
- How severe is CVE-2026-89027?
- Medium severity, with a CVSS score of 6.5, published 15 September 2026.
- Which products and versions are affected?
- miniOrange JWT Authentication for WP REST APIs before 4.8.0.
- Is there a fix for CVE-2026-89027?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-89027 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-89027?
- Check whether you run miniOrange JWT Authentication for WP REST APIs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication method downgrade flaw in miniOrange JWT Authentication for WP REST APIs before version 4.8.0. An unauthenticated attacker can supply a specific GET parameter to bypass administrator-configured authentication mechanisms (JWT, API tokens, etc.) without capability checks or nonce verification, forcing the plugin to use Basic HTTP authentication instead. The attacker can then exploit distinguishable error codes and the absence of rate limiting to conduct unthrottled username enumeration and credential guessing attacks against the WordPress REST API. The vulnerability is classified as CWE-306 (Missing Authentication for Critical Function) and requires only network access with no user interaction or authentication required.
Affected products
- miniOrange JWT Authentication for WP REST APIs before 4.8.0
Timeline
- 2026-09-15: disclosed