{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8198 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8198 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8198 is a medium-severity authentication bypass vulnerability in Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity, published on 9 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8198 and fix it if it is affected.\n\nWhat it is: CVE-2026-8198 is a medium-severity authentication bypass vulnerability in Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity, published on 9 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-8198 in the wild and no public exploit code.\n\nAffected product: Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-8198/ (Markdown: https://insights.sbomify.com/CVE-2026-8198/index.md)","id":"CVE-2026-8198","markdown":"https://insights.sbomify.com/CVE-2026-8198/index.md","name":"CVE-2026-8198","record":{"aliases":["GHSA-5rh7-8226-g7fr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication to access REST API endpoints and retrieve sensitive plugin configuration data, including API keys.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity","id":"CVE-2026-8198","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Post-auth memory exhaustion via bitwise match expressions","id":"CVE-2026-8199"},"packages":[],"prev":{"headline":"Concrete CMS 9.5.0 and below is vulnerable to Stored XSS via OAuth integration name","id":"CVE-2026-8197"},"products":["Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity"],"published":"2026-05-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["logtivity"]},"summary":"Unauthenticated attackers can bypass authentication to access REST API endpoints and retrieve sensitive plugin configuration data, including API keys.","url":"https://insights.sbomify.com/CVE-2026-8198/"}