REST API Log <= 1.7.1 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 1.7.2
- Affected Plugin
- REST API Log
- Affected Version
<= 1.7.1- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-66443
At a glance
CVE-2026-66443 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the REST API Log WordPress plugin, affecting versions <= 1.7.1. 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.2; sites on affected versions should update now. Disclosed August 2026, reported by Aydan Arabadzha.
Vulnerability Overview
The REST API Log plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.7.1. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in REST API Log <= 1.7.1 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For REST API Log the fix is 1.7.2: builds <= 1.7.1 are affected, anything from 1.7.2 onward is not.
Remediation
Update to version 1.7.2, 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.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C