REST API Log <= 1.7.0 - Missing Authorization to Unauthenticated Sensitive Log Data Disclosure
Strategic Overview
- Status
- Patched in 1.7.1
- Affected Plugin
- REST API Log
- Affected Version
<= 1.7.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-16547
At a glance
CVE-2026-16547 is a medium-severity Missing Authorization vulnerability in the REST API Log WordPress plugin, affecting versions <= 1.7.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7.1; sites on affected versions should update now. Disclosed July 2026, reported by Shikhali Jamalzade.
Vulnerability Overview
The REST API Log plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 1.7.0. This is due to missing authentication check in the download_permissions_check() function, which only validated a time-based hash without verifying the requesting user had the required capability to read log entries. This makes it possible for unauthenticated attackers to download sensitive REST API log data without authentication by accessing the download endpoint with a valid hash.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
REST API Log <= 1.7.0 carries this weakness at download_permissions_check(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For REST API Log the fix is 1.7.1: builds <= 1.7.0 are affected, anything from 1.7.1 onward is not.
Remediation
Update to version 1.7.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: REST API Log 1.7.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in REST API Log
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C