Is REST API Log safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.7.3). As of 2026-11-04. 3 issues are on record for older versions; version 1.7.3 or newer fixes all of them that state a fix. Keep REST API Log on the latest version (1.7.3) and remove it if you do not use it.

Which versions of REST API Log are vulnerable?

Known issues on record (newest first): Missing authorization check (1.7.2 and older, fixed in 1.7.3); Information disclosure (1.7.1 and older, fixed in 1.7.2); Missing authorization check (older than 1.7.1, fixed in 1.7.1). The full list with sources is on this page.

What is the latest version of REST API Log?

1.7.3, according to wordpress.org (last updated 2026-09-25). It has 5,000+ active installs.

What should I do if my REST API Log is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-rest-api-log). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · wp-rest-api-log · data as of 2026-11-04

Is REST API Log safe? Known vulnerabilities and latest version

Latest version: 1.7.3
Last updated: 2026-09-25
Active installs: 5,000+
Known issues on record: 3
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

WordPress plugin to log REST API requests and responses — by Pete Nelson

What to do

Update to the latest version (1.7.3). Anything older than 1.7.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get wp-rest-api-log --field=version shows what you run; wp plugin update wp-rest-api-log updates it.

Check your version

Known vulnerabilities

3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.5 CVE-2026-100514 · published 2026-10-01

Missing authorization check in REST API Log (1.7.2 and older)

Affected: 1.7.2 and older
Fixed in: 1.7.3
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Insecure Direct Object References (IDOR) in REST API Log <= 1.7.2 versions.

NVD CVE-2026-100514 Patchstack advisory

high 7.5 CVE-2026-66443 · published 2026-08-13

Information disclosure in REST API Log (1.7.1 and older)

Affected: 1.7.1 and older
Fixed in: 1.7.2
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Sensitive Data Exposure in REST API Log <= 1.7.1 versions.

NVD CVE-2026-66443 Patchstack advisory

medium 5.9 CVE-2026-16547 · published 2026-08-04

Missing authorization check in REST API Log (older than 1.7.1)

Affected: older than 1.7.1
Fixed in: 1.7.1
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

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.

NVD CVE-2026-16547 WPScan advisory

Recent activity

2026-09-25 — latest release on wordpress.org (1.7.3).
2026-10-01 — Missing authorization check disclosed (CVE-2026-100514), fixed in 1.7.3.
2026-08-13 — Information disclosure disclosed (CVE-2026-66443), fixed in 1.7.2.
2026-08-04 — Missing authorization check disclosed (CVE-2026-16547), fixed in 1.7.1.

Free. We check the CVE feeds every day and email you only when a new issue for REST API Log (wp-rest-api-log) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (2) · Sensitive data exposure (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wp-rest-api-log (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/wp-rest-api-log"><img src="https://laskyr.com/plugins/wp-rest-api-log/badge.svg" alt="REST API Log vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is REST API Log safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (1.7.3)

What to do

Check your version

Known vulnerabilities

Missing authorization check in REST API Log (1.7.2 and older)

Information disclosure in REST API Log (1.7.1 and older)

Missing authorization check in REST API Log (older than 1.7.1)

Recent activity

Get an email when REST API Log has a new vulnerability

Browse vulnerabilities

Where this data comes from