The Burst Statistics WordPress plugin before 3.7.5 does not enforce a shared report's date range on the analytics it
Source GCVE Database
Not known to be exploited : upgrade to 3.7.5 when convenient.
Data as of 15 Nov 2026, 10:39 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.7.5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade Burst Statistics (WordPress plugin) to 3.7.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Burst Statistics | Affected
| Fixed in
|
AI-suggested
Upgrade the Burst Statistics WordPress plugin to version 3.7.5 or later, where this issue is fixed. No other mitigation guidance is provided, and no indication that the vulnerability is already mitigated without patching.
Description
The Burst Statistics WordPress plugin versions before 3.7.5 do not properly enforce the date range on shared analytics reports. This flaw allows anyone with access to a shared report link to view statistics for any date range retained by the site, not just the intended shared period.