CVE-2026-8198: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in logtivity Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity
The Logtivity WordPress plugin (Activity Logs, User Activity Tracking, Multisite Activity Log) versions up to 3. 3. 6 contain an authentication bypass vulnerability. Due to a logic flaw in the verifyAuthorization method, requests missing an Authorization header bypass Bearer token validation and are granted access. This allows unauthenticated attackers to access the /wp-json/logtivity/v1/options REST API endpoint and retrieve sensitive plugin configuration data, including the logtivity_site_api_key. The exposed API key can be used to impersonate the site in API calls to the Logtivity service. The vulnerability has a CVSS score of 5. 3, indicating medium severity. No official patch or remediation guidance is currently available from the vendor.
AI Analysis
Technical Summary
CVE-2026-8198 is an authentication bypass vulnerability in the Logtivity WordPress plugin's verifyAuthorization method. The flaw causes requests without an Authorization header to skip Bearer token validation and return true unconditionally, allowing unauthenticated access to sensitive plugin configuration via the /wp-json/logtivity/v1/options REST API endpoint. This exposure includes the logtivity_site_api_key, which can be leveraged to impersonate the site in API interactions with the Logtivity service. The vulnerability affects versions up to and including 3.3.6. No vendor-provided patch or official remediation is currently documented.
Potential Impact
An unauthenticated attacker can retrieve sensitive configuration information from the plugin, including the logtivity_site_api_key. This key exposure can enable impersonation of the affected site in API calls to the Logtivity service, potentially leading to unauthorized actions or data access within that service context. The vulnerability does not directly impact integrity or availability but compromises confidentiality of sensitive data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the WordPress REST API endpoints where possible, and monitor for updates from the Logtivity vendor regarding patches or mitigations. Avoid exposing the /wp-json/logtivity/v1/options endpoint publicly if feasible.
CVE-2026-8198: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in logtivity Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity
Description
The Logtivity WordPress plugin (Activity Logs, User Activity Tracking, Multisite Activity Log) versions up to 3. 3. 6 contain an authentication bypass vulnerability. Due to a logic flaw in the verifyAuthorization method, requests missing an Authorization header bypass Bearer token validation and are granted access. This allows unauthenticated attackers to access the /wp-json/logtivity/v1/options REST API endpoint and retrieve sensitive plugin configuration data, including the logtivity_site_api_key. The exposed API key can be used to impersonate the site in API calls to the Logtivity service. The vulnerability has a CVSS score of 5. 3, indicating medium severity. No official patch or remediation guidance is currently available from the vendor.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-8198 is an authentication bypass vulnerability in the Logtivity WordPress plugin's verifyAuthorization method. The flaw causes requests without an Authorization header to skip Bearer token validation and return true unconditionally, allowing unauthenticated access to sensitive plugin configuration via the /wp-json/logtivity/v1/options REST API endpoint. This exposure includes the logtivity_site_api_key, which can be leveraged to impersonate the site in API interactions with the Logtivity service. The vulnerability affects versions up to and including 3.3.6. No vendor-provided patch or official remediation is currently documented.
Potential Impact
An unauthenticated attacker can retrieve sensitive configuration information from the plugin, including the logtivity_site_api_key. This key exposure can enable impersonation of the affected site in API calls to the Logtivity service, potentially leading to unauthorized actions or data access within that service context. The vulnerability does not directly impact integrity or availability but compromises confidentiality of sensitive data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the WordPress REST API endpoints where possible, and monitor for updates from the Logtivity vendor regarding patches or mitigations. Avoid exposing the /wp-json/logtivity/v1/options endpoint publicly if feasible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-08T23:39:09.229Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69ff2a48cbff5d8610194c7f
Added to database: 5/9/2026, 12:36:24 PM
Last enriched: 5/9/2026, 12:51:24 PM
Last updated: 5/9/2026, 3:51:33 PM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.