Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity <= 3.3.6 - Unauthenticated Information Disclosure via REST API
Strategic Overview
- Status
- Patched in 3.3.7
- Affected Version
<= 3.3.6- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-8198
At a glance
CVE-2026-8198 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity WordPress plugin, affecting versions <= 3.3.6. 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 3.3.7; sites on affected versions should update now. Disclosed May 2026, reported by Ronnachai Chaipha (rxnr).
Vulnerability Overview
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.
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 Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity <= 3.3.6 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 Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity the fix is 3.3.7: builds <= 3.3.6 are affected, anything from 3.3.7 onward is not.
Remediation
Update to version 3.3.7, 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: Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity 3.3.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C