CVE-2026-19715 WP OAuth Server < 6.3.1 - Unauthenticated OAuth Token and User Data Disclosure via Debug Log File

High 7.5 Published Updated

Unauthenticated attackers can read sensitive OAuth tokens and user data from publicly accessible debug logs if logging is enabled.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-19715?

CVE-2026-19715 is a high-severity vulnerability in Unknown WP OAuth Server ( Login with WordPress ), published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

The WP OAuth Server ( Login with WordPress ) WordPress plugin before 6.3.1 does not restrict access to the debug log it writes, which is stored at a fixed and publicly reachable location, allowing unauthenticated users to read the OAuth tokens and authorisation codes it has issued as well as user records including password hashes when debug logging is enabled.

Weakness: CWE-200

Which versions are affected by CVE-2026-19715?

How do I fix CVE-2026-19715?

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

Is CVE-2026-19715 being exploited?

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

Sources

Also known as GHSA-fjp2-v4jv-4x75.

Is CVE-2026-19715 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free