Hackers Exploit Auth Bypass in Burst Statistics WordPress Plugin

Overview A critical flaw in the Burst Statistics WordPress plugin (CVE‑2026‑8181) is being actively exploited, giving attackers admin‑level access to vulnerable sites. Burst Statistics, a privacy‑focused analytics tool with over 200,000 active installations, was marketed as a lightweight alternative to Google Analytics. The vulnerability was introduced in version 3.4.0 (April 23, 2026) and persisted in 3.4.1.

Vulnerability Details

  • Root Cause: Misinterpretation of the wp_authenticate_application_password() function.
    • WP_Error and null values were incorrectly treated as successful authentication.
  • Attack Method:
    • Attackers supply a valid admin username with any arbitrary password in a Basic Auth header.
    • The plugin calls wp_set_current_user() with the attacker’s username, impersonating the admin.
  • Impact:
    • Full impersonation of admin users during REST API requests.
    • Ability to create rogue admin accounts without prior authentication.

Exploitation in the Wild

  • Wordfence Discovery: Reported CVE‑2026‑8181 on May 8, 2026.
  • Active Attacks: Over 7,400 exploit attempts blocked in 24 hours.
  • Exposure: Admin usernames often leak via blog posts, comments, or public API requests, making exploitation easier.
  • Risks:
    • Database access.
    • Malware distribution.
    • Redirecting visitors to unsafe sites.
    • Planting persistent backdoors.

Mitigation

  • Update Immediately: Upgrade to version 3.4.2 (released May 12, 2026).
  • Disable Plugin: If patching isn’t possible, disable Burst Statistics until secure.
  • Current Exposure: WordPress.org stats show ~85,000 downloads of 3.4.2, leaving 115,000 sites still vulnerable.

Final Thought

This incident highlights the high‑risk nature of WordPress plugin vulnerabilities. With attackers already exploiting CVE‑2026‑8181 at scale, site owners must patch immediately or disable the plugin. For defenders, the lesson is clear: REST API endpoints are prime targets, and authentication logic must be rigorously validated.

Be the first to comment

Leave a Reply

Your email address will not be published.


*


This site uses Akismet to reduce spam. Learn how your comment data is processed.