CVE-2026-16547

REST API Log < 1.7.1 - Unauthenticated Sensitive Log Data Disclosure via Download Endpoint

Published Aug 4, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The REST API Log WordPress plugin allows any user who knows the download token to retrieve logged REST API requests and responses for any entry. Because the plugin does not associate the token with a specific log entry and does not verify the requester's permissions, attackers can obtain logs that may contain credentials, authentication tokens, or private content. This flaw is a CWE‑284 Improper Access Control vulnerability and constitutes an unauthorized disclosure of sensitive information.

Affected Systems

WordPress installations running the REST API Log plugin at any version prior to 1.7.1 are affected. The plugin's documentation indicates that the vulnerability exists in all releases below the 1.7.1 update, which addresses the token binding and capability checks.

Risk and Exploitability

The risk is amplified by the lack of an access control check; any person with a token can abuse the download endpoint. The EPSS score is less than 1% and the vulnerability is not listed in CISA KEV, and the CVSS score of 5.9 indicates medium severity. An exploit requires only the possession of a valid token; it is inferred that the token could be leaked or guessed, which would make the vulnerability feasibly exploitable in many environments where the plugin is exposed to the internet.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the REST API Log plugin to version 1.7.1 or later to enforce token binding and capability verification.
  • Restrict access to the /download endpoint by configuring WordPress or the web server to require authentication for all requests to the endpoint.
  • Invalidate any pre‑existing download tokens after the upgrade and remove or secure old log files that may still contain sensitive data.

Generated by OpenCVE AI on August 4, 2026 at 20:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Pete Nelson
Pete Nelson rest Api Log
Wordpress
Wordpress wordpress
Vendors & Products Pete Nelson
Pete Nelson rest Api Log
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-284
Type Values Removed Values Added
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.
Title REST API Log < 1.7.1 - Unauthenticated Sensitive Log Data Disclosure via Download Endpoint
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 4, 2026, 2:05 PM
Reserved
Jul 22, 2026, 10:12 AM
Status
Deferred
Published
Aug 4, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM