{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-42673 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-42673 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42673 is a high-severity vulnerability in Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity, published on 1 Jun 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-42673 and fix it if it is affected.\n\nWhat it is: CVE-2026-42673 is a high-severity vulnerability in Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity, published on 1 Jun 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-42673 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-42673/ (Markdown: https://insights.sbomify.com/CVE-2026-42673/index.md)","id":"CVE-2026-42673","markdown":"https://insights.sbomify.com/CVE-2026-42673/index.md","name":"CVE-2026-42673","record":{"aliases":["GHSA-873w-p97p-f26x"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can retrieve embedded sensitive data from sent information in the Logtivity WordPress plugin, exposing private user details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"Insertion of Sensitive Information Into Sent Data vulnerability in Logtivity Activity Logs Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity allows Retrieve Embedded Sensitive Data.\n\nThis issue affects Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity: from n/a through 3.3.6.","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":"Information disclosure in Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity","id":"CVE-2026-42673","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Advanced Access Manager plugin \u003c= 7.1.0 - Bypass Vulnerability vulnerability","id":"CVE-2026-42674"},"packages":[],"prev":{"headline":"WordPress WP Directory Kit plugin \u003c= 1.5.1 - SQL Injection vulnerability","id":"CVE-2026-42672"},"products":["Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity"],"published":"2026-06-01","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-06-01","vendors":["Logtivity Activity Logs"]},"summary":"Attackers can retrieve embedded sensitive data from sent information in the Logtivity WordPress plugin, exposing private user details.","url":"https://insights.sbomify.com/CVE-2026-42673/"}