Quick answers
- Is CVE-2026-19715 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19715 being exploited in the wild.
- How severe is CVE-2026-19715?
- High severity, with a CVSS score of 7.5, published 27 August 2026.
- Which products and versions are affected?
- miniOrange WP OAuth Server before 6.3.1.
- Is there a fix for CVE-2026-19715?
- A patch was published on 2026-08-25: Fixed in version 6.3.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19715 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-19715?
- Check whether you run miniOrange WP OAuth Server 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 information disclosure issue (CWE-200) caused by insufficient access controls on debug log files. The plugin stores logs at a fixed, web-accessible path (wp-content/uploads/miniorange-oauth-20-server/error-logs/wp_oauth_server_errors.log) without authentication or authorization checks. When debug logging is enabled, these logs contain unencrypted OAuth tokens, refresh tokens, authorization codes, and full WordPress user records including password hashes. An unauthenticated attacker can directly access this file via HTTP GET and retrieve active tokens to authenticate as any user who has completed an OAuth authorization flow. The vulnerability requires debug logging to be enabled but does not require network authentication or user interaction. Versions before 6.3.1 are affected; the issue is patched in 6.3.1.
Affected products
- miniOrange WP OAuth Server before 6.3.1
Timeline
- 2026-08-25: disclosed
- 2026-08-27: advisory
- 2026-08-25: patched: Fixed in version 6.3.1