Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
CVE-2026-97343
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.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard