REST API Log download tokens are not bound to individual entries
REST API Log before 1.7.1 protects log downloads with a token but does not bind that token to the requested log entry or verify the requester's capability. An unauthenticated caller who obtains any valid download token can change the requested entry and retrieve other logged REST API requests and responses, potentially exposing credentials, authentication tokens or private content. The public advisory does not disclose the download route, token parameter, entry parameter or validation function.
- Component
- REST API Log
- Plugin slug
rest-api-log- Affected
- < 1.7.1
- Safe version
1.7.1- Published
- Aug 04, 2026
This CVE was published Aug 04, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update REST API Log to 1.7.1 or later. Rotate credentials or authentication tokens found in logged traffic and review downloads or enumeration attempts if any valid log token may have been exposed.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The REST API Log WordPress plugin before 1.7.1 does not bind the token protecting its log download feature to the log entry being requested, nor does it check the capability of the requester, allowing unauthenticated users in possession of any such token to download the logged REST API requests and responses of any entry, which may contain sensitive data such as credentials, authentication tokens or private content.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N