dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-8198

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Logtivity WordPress plugin contains an authentication bypass vulnerability in its REST API due to a logic flaw in the verifyAuthorization method. When incoming requests lack an Authorization header, the Bearer token validation is skipped and the code falls through to an unconditional return true statement, effectively bypassing all authentication checks. This allows unauthenticated attackers to access the /wp-json/logtivity/v1/options endpoint and retrieve sensitive configuration including the logtivity_site_api_key.

MitigationUpdate the Logtivity plugin to version 3.3.7 or later to remediate this authentication bypass. Until patched, consider disabling the REST API endpoint or restricting access via server-level authentication rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Logtivity plugin is installed
    Check for the Logtivity plugin directory in your WordPress installation at /wp-content/plugins/ or view the installed plugins list via WordPress admin under Plugins > Installed Plugins.
    Affected if The Logtivity plugin appears in the list of installed WordPress plugins.
  2. Determine installed Logtivity version
    Access the plugin file header (typically logtivity.php) in the plugin directory and locate the 'Version' comment, or view the version in WordPress admin under Plugins > Installed Plugins next to the Logtivity entry.
    Affected if The installed version is lower than 3.3.7, as versions prior to this release contain the authentication bypass in the verifyAuthorization method.
  3. Verify REST API endpoint responds without authentication
    Send a GET request to /wp-json/logtivity/v1/options using a tool like curl or a browser, without including any Authorization header. Example: curl -s https://yourdomain.com/wp-json/logtivity/v1/options
    Affected if The endpoint returns a 200 OK response with JSON data (including potentially the site API key) without requiring authentication, indicating the vulnerability is present and exploitable.
  4. Inspect endpoint response for sensitive data exposure
    Examine the JSON response from the unauthenticated /wp-json/logtivity/v1/options request. Look for fields such as 'api_key', 'site_api_key', or similar sensitive configuration values in the response body.
    Affected if The response contains the site API key or other sensitive plugin settings, confirming the authentication bypass allows exfiltration of credentials.

A user is affected if the Logtivity plugin version is below 3.3.7 AND the /wp-json/logtivity/v1/options endpoint returns sensitive data (including the API key) without requiring an Authorization header.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Logtivity plugin to version 3.3.7 or later to remediate this authentication bypass. Until patched, consider disabling the REST API endpoint or restricting access via server-level authentication rules.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8198 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data