CVE-2026-97343: Burst Statistics <= 3.7.1 - Improper Authentication to Account Persistence via Share-Link Authentication Bypass via 'burst_share_token'
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 maybeloadshareddashboard() handler issuing a genuine WordPress session cookie for the burststatisticsviewer account to any visitor presenting a valid share token via wpsetauthcookie(), while the plugin only blocks Application Passwords for the resulting burstviewer role and does not restrict the core /wp-json/wp/v2/users/me password update endpoint or filter the edituser 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 burststatisticsviewer WordPress account, constituting a permanent takeover of that limited-privilege (viewburststatistics) account that persists through share-token revocation, share-token expiration, and execution of the plugin's daily cleanupviewersessions() routine. Exploitation requires that the attacker have obtained a valid burstsharetoken, such as one that has been shared publicly or distributed to an untrusted party.
Affected Software
Event History
Frequently Asked Questions
What does an attacker need to exploit this issue?
The attacker needs a valid share token. Presenting that token causes the plugin to issue a genuine WordPress session cookie for the burst_statistics_viewer account.
Will revoking or expiring a share token remove an attacker's access?
No. An attacker who uses the issue to set a chosen password can retain access to the burst_statistics_viewer account after share-token revocation, token expiration, and the plugin's daily cleanup_viewer_sessions() routine.
What level of access can be retained through this vulnerability?
The persistent account is limited to the burst_viewer role and the view_burst_statistics capability. The described impact is takeover of that limited-privilege WordPress account, not an administrator account.