CVE-2026-7634: SlimStat Analytics (WordPress plugin) · Cross-site Scripting
Affects SlimStat Analytics (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 May 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| veronalabsSlimStat Analytics | Affected
| Fixed in– |
AI-suggested
Until a fix is available, administrators should ensure the show_complete_user_agent_tooltip setting remains disabled to prevent exploitation. Monitor official vendor channels for updates and apply any released patches promptly.
Description
The SlimStat Analytics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'User-Agent' header in all versions up to, and including, 5.4.11 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The show_complete_user_agent_tooltip setting must be explicitly enabled by an administrator (disabled by default) for the stored payload to be rendered and executed.
References
- wordfence.com/threat-intel/vulnerabilities/id/0a309bf8-7fe3-4033-993c-3c8dba0f216d?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/trunk/admin/view/wp-slimstat-reports.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.11/admin/view/wp-slimstat-reports.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/trunk/src/Tracker/Storage.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.11/src/Tracker/Storage.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/trunk/src/Tracker/Processor.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.11/src/Tracker/Processor.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/trunk/src/Services/Browscap.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.11/src/Services/Browscap.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.4/admin/view/wp-slimstat-reports.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.4/src/Tracker/Storage.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.4/src/Tracker/Processor.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-slimstat/tags/5.4.4/src/Services/Browscap.php (opens in a new tab)
- github.com/wp-slimstat/wp-slimstat/pull/297 (opens in a new tab)