CVE-2026-7634 json
SlimStat Analytics <= 5.4.11 - Unauthenticated Stored Cross-Site Scripting via User-Agent Header
published 5mo ago modified 4mo ago also EUVD-2026-32729
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/wp-slimstat/wp-slimstat#297 pull request
Is CVE-2026-7634 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- veronalabs SlimStat Analytics
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- github.com /wp-slimstat/wp-slimstat/pull/297
- wordfence.com /threat-intel/vulnerabilities/id/0a309bf8-7fe3-4033-993c-3c8dba0f216d?source=cve
- plugins.trac.wordpress.org /browser/wp-slimstat/trunk/admin/view/wp-slimstat-reports.php#L2099
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.11/admin/view/wp-slimstat-reports.php#L2099
- plugins.trac.wordpress.org /browser/wp-slimstat/trunk/src/Tracker/Storage.php#L25
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.11/src/Tracker/Storage.php#L25
- plugins.trac.wordpress.org /browser/wp-slimstat/trunk/src/Tracker/Processor.php#L776
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.11/src/Tracker/Processor.php#L776
- plugins.trac.wordpress.org /browser/wp-slimstat/trunk/src/Services/Browscap.php#L270
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.11/src/Services/Browscap.php#L270
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.4/admin/view/wp-slimstat-reports.php#L2099
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.4/src/Tracker/Storage.php#L25
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.4/src/Tracker/Processor.php#L776
- plugins.trac.wordpress.org /browser/wp-slimstat/tags/5.4.4/src/Services/Browscap.php#L270
Sources
- CVE List CVE-2026-7634
- NVD CVE-2026-7634
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.