Rest Api Log
Monthly
Unauthenticated sensitive data exposure in the REST API Log WordPress plugin (versions <= 1.7.1) allows any remote actor to query the plugin's log storage and retrieve recorded REST API request and response data without credentials. Reported by Patchstack and scored CVSS 7.5 (High) with AV:N/AC:L/PR:N/UI:N, the exposure is trivially reachable across the network with no authentication or user interaction. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Broken object-level authorization in the REST API Log WordPress plugin (all versions before 1.7.1) permits unauthenticated attackers who hold any valid log-download token - regardless of which entry it was issued for - to retrieve arbitrary log entries from any other user, exposing stored credentials, authentication tokens, and private REST API payloads. The root cause is twofold: tokens are not cryptographically bound to specific log entry IDs, and the plugin performs no WordPress capability check on the requester. A public exploit PoC is referenced via WPScan, though EPSS at 0.18% and SSVC exploitation status of 'none' indicate no confirmed widespread abuse at time of analysis.
Unauthenticated sensitive data exposure in the REST API Log WordPress plugin (versions <= 1.7.1) allows any remote actor to query the plugin's log storage and retrieve recorded REST API request and response data without credentials. Reported by Patchstack and scored CVSS 7.5 (High) with AV:N/AC:L/PR:N/UI:N, the exposure is trivially reachable across the network with no authentication or user interaction. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Broken object-level authorization in the REST API Log WordPress plugin (all versions before 1.7.1) permits unauthenticated attackers who hold any valid log-download token - regardless of which entry it was issued for - to retrieve arbitrary log entries from any other user, exposing stored credentials, authentication tokens, and private REST API payloads. The root cause is twofold: tokens are not cryptographically bound to specific log entry IDs, and the plugin performs no WordPress capability check on the requester. A public exploit PoC is referenced via WPScan, though EPSS at 0.18% and SSVC exploitation status of 'none' indicate no confirmed widespread abuse at time of analysis.