WordPress security changelog
MEDIUM CVE-2026-8198 Deferred

Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity: Privilege escalation or authentication bypass

Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity is affected by privilege escalation or authentication bypass. The vulnerable path is reachable without authentication. A successful request can grant permissions or access that the caller should not possess. The published affected range is <= 3.3.6.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity
Plugin slug
logtivity
Affected
<= 3.3.6
Safe version
> 3.3.6
Published
May 09, 2026
Weakness
CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor

This CVE was published May 09, 2026 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity to a release after 3.3.6, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity plugin for WordPress is vulnerable to Authentication Bypass to Information Disclosure in versions up to, and including, 3.3.6. This is due to a logic flaw in the verifyAuthorization method where requests without an Authorization header skip Bearer token validation and fall through to an unconditional return true statement, bypassing all authentication checks. This makes it possible for unauthenticated attackers to access the /wp-json/logtivity/v1/options REST API endpoint and retrieve all plugin configuration options, including the logtivity_site_api_key which can be used to impersonate the site in API calls to the Logtivity service.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

Primary and upstream sources