CVE-2026-97343
MEDIUMDescription
The Burst Statistics – Simple WordPress Analytics (Google Analytics Alternative) plugin for WordPress is vulnerable to Improper Authentication leading to Account Persistence in all versions up to, and including, 3.7.1. This is due to the `maybe_load_shared_dashboard()` handler issuing a genuine WordPress session cookie for the `burst_statistics_viewer` account to any visitor presenting a valid share token via `wp_set_auth_cookie()`, while the plugin only blocks Application Passwords for the resulting `burst_viewer` role and does not restrict the core `/wp-json/wp/v2/users/me` password update endpoint or filter the `edit_user` capability for that account — leaving WordPress core's built-in rule that any authenticated user may update their own account fully in effect. This makes it possible for unauthenticated attackers to set an attacker-chosen password on the `burst_statistics_viewer` WordPress account, constituting a permanent takeover of that limited-privilege (`view_burst_statistics`) account that persists through share-token revocation, share-token expiration, and execution of the plugin's daily `cleanup_viewer_sessions()` routine. Exploitation requires that the attacker have obtained a valid `burst_share_token`, such as one that has been shared publicly or distributed to an untrusted party.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-287 (Improper Authentication) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-7593 | Critical | 9.8 | 100% | KEV | - |
| CVE-2023-35082 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-35078 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2017-7921 | Critical | 9.8 | 100% | KEV | - |
| CVE-2021-33044 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2023-46805 | High | 8.2 | 100% | KEV + Ransom | - |
Common questions
How do I fix CVE-2026-97343?
No published fix for CVE-2026-97343 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-97343?
CVE-2026-97343 has a CVSS v3 base score of 4.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-97343
Markdown
[](https://tridentstack.com/cve/CVE-2026-97343)HTML
<a href="https://tridentstack.com/cve/CVE-2026-97343"><img src="https://tridentstack.com/cve/badge/CVE-2026-97343.svg" alt="CVE-2026-97343"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-03.