Authentication Bypass in Burst Statistics – Simple WordPress Analytics (WordPress plugin) (CVE-2026-97343)
Summary
Authentication bypass in Burst Statistics – Simple WordPress Analytics (WordPress plugin) (CVE-2026-97343). Risk of unauthorized operations or information disclosure. Exploitable via burst_statistics_viewer.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-97343 has been found in Burst Statistics – Simple WordPress Analytics (WordPress plugin).
Attackers can target a specific entry point like burst_statistics_viewer over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Burst Statistics – Simple WordPress Analytics (WordPress plugin) CVE-2026-97343" on the vendor's site.
CVE-2026-97343 (Burst Statistics – Simple WordPress Analytics (WordPress plugin)) — CWE-287 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: burst_statistics_viewer / burst_viewer / edit_user / view_burst_statistics
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in Burst Statistics – Simple WordPress Analytics (WordPress plugin). Attackers reach the vulnerable code path via burst_statistics_viewer.
Check the vendor advisory for the affected versions of Burst Statistics – Simple WordPress Analytics (WordPress plugin). Attack surface: burst_statistics_viewer / burst_viewer / edit_user / view_burst_statistics.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Burst Statistics – Simple WordPress Analytics (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web nvd.nist.gov
- web github.com