Skip to main content

Wp Statistics Simple Privacy Friendly Google Analytics Alternative EUVDEUVD-2026-23342

| CVE-2026-5231 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-04-17 Wordfence
7.2
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Craft malicious URL with XSS payload in utm_source parameter
  2. Delivery
    Distribute link via SEO/social/email to drive site traffic
  3. Exploit
    WP Statistics logs unsanitized payload to database
  4. Install
    Administrator accesses Referrals/Social Media dashboard
  5. C2
    chart.js renders stored payload via innerHTML
  6. Execute
    JavaScript executes in admin context
  7. Impact
    Attacker achieves session hijacking or privilege escalation

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the WP Statistics plugin to be installed and actively tracking referral data (default behavior when plugin is activated). The vulnerable ReferralsParser wildcard channel matching logic must process incoming requests - this occurs for any page visit with utm_source parameters when referral tracking is enabled. No special WordPress configuration, non-default plugin settings, or administrative authentication is required for the injection phase. However, payload execution specifically requires an administrator to navigate to either the 'Referrals Overview' or 'Social Media' analytics pages in the WordPress admin dashboard (WP Statistics → Referrals or WP Statistics → Social Media menu paths). Sites where administrators never access these specific analytics views remain vulnerable to injection but would not experience payload execution. The vulnerability affects default installations with standard chart rendering enabled.

Impact

CVSS 7.2 (High) with AV:N/AC:L/PR:N/UI:N indicates trivial remote exploitation requiring no authentication or user interaction for the injection phase. However, the S:C (Changed Scope) and UI requirements deserve nuance: attackers can inject payloads unauthenticated by simply visiting the WordPress site with crafted utm_source parameters, but payload execution requires an administrator to subsequently view specific analytics pages. This two-stage attack (unauthenticated write, privileged read) means CVSS overstates immediate risk - the UI:N rating applies to injection, not execution. Real-world exploitation requires attackers to drive traffic with malicious UTM parameters (trivial via link campaigns, SEO poisoning, or referrer spoofing) then wait for admin chart access. EPSS data not provided, but no CISA KEV listing indicates no confirmed widespread exploitation. The public Wordfence disclosure and Trac browser links showing vulnerable code increase POC feasibility. Risk is MODERATE-HIGH for sites with this plugin where admins regularly review analytics (common use case), but lower for installations where dashboards are rarely accessed. The Changed Scope (S:C) rating is appropriate as JavaScript executes in admin context with elevated WordPress privileges beyond the plugin's intended boundary.

Exploit ScenarioDerived

An attacker crafts a URL to the target WordPress site appending a malicious utm_source parameter containing JavaScript payload, such as example.com/?utm_source=<img src=x onerror=alert(document.cookie)>. The attacker distributes this link via social media, email campaigns, or SEO poisoning to drive traffic. When visitors click the link, WP Statistics logs the utm_source value into its referral database without sanitization. Days or weeks later, a WordPress administrator accesses the plugin's Referrals Overview dashboard to review traffic sources. The chart rendering code injects the stored payload into the page via innerHTML, executing the attacker's JavaScript with the administrator's session privileges, enabling cookie theft, privilege escalation, or further site compromise.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Apr 17, 2026

Stored Cross-Site Scripting in WP Statistics plugin (≤14.16.4) allows unauthenticated attackers to inject malicious JavaScript into admin dashboard analytics pages. The vulnerability stems from unsafe handling of utm_source URL parameters that persist into database-backed charts, executing when administrators view Referrals Overview or Social Media pages. With CVSS 7.2 and network vector requiring no authentication, this represents elevated risk for WordPress sites using this analytics plugin, though no active exploitation confirmed at time of analysis.

Earlier versions of this analysis (1)
v1 Apr 17, 2026 - 02:18 CVSS 7.2

Stored Cross-Site Scripting in WP Statistics plugin (all versions ≤14.16.4) allows unauthenticated remote attackers to inject malicious JavaScript into WordPress admin dashboards via crafted utm_source parameters in HTTP referrals. Injected scripts execute when administrators view Referrals Overview or Social Media analytics charts, enabling session hijacking, privilege escalation, or persistent backdoor installation. CVSS 7.2 with scope change (S:C) reflects cross-context impact from unauthenticated visitor to admin session. EPSS data not provided; no CISA KEV listing identified. Wordfence disclosure includes direct source code references to vulnerable parsing (ReferralsParser.php line 62) and rendering (chart.js line 498) functions.

RemediationAI

Upgrade WP Statistics plugin to version 14.16.5 or later, which addresses the XSS vulnerability per the Trac changeset at https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3503795%40wp-statistics%2Ftrunk&old=3483860%40wp-statistics%2Ftrunk. The patch implements proper output escaping in chart.js rendering and input sanitization in ReferralsParser.php. If immediate patching is not feasible, disable the Referrals Overview and Social Media analytics features in WP Statistics settings to prevent payload execution (this removes vulnerable chart rendering but eliminates referral tracking functionality). Alternatively, restrict WordPress admin dashboard access to trusted networks via .htaccess IP whitelisting or firewall rules, reducing exposure to payload execution (does not prevent injection, only limits who can trigger execution). Review existing analytics data for anomalous utm_source entries containing HTML/JavaScript syntax and purge suspicious records from the database statistics tables. No workaround fully mitigates the vulnerability without applying the vendor patch.

Affected VersionsENISA

WP Statistics – Simple, privacy-friendly Google Analytics alternative 0 ≤14.16.4

Affected Packages

euvd wp_statistics_simple_privacy_friendly_google_analytics_alternative no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WP Statistics is a WordPress analytics plugin (cpe:2.3:a:veronalabs:wp_statistics) that tracks visitor referrals and UTM campaign parameters. The vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation) exists in the referral parsing pipeline. When processing incoming traffic with utm_source parameters, the ReferralsParser.php (line 62) copies raw utm_source values directly into the source_name database field when wildcard channel domain patterns match. Later, chart.js (line 498) renders this stored data into chart legends using innerHTML without HTML escaping. This creates a classic stored XSS where attacker-controlled URL parameters become persistent database content that executes JavaScript in administrative contexts. The attack surface is the public-facing WordPress site (any page accepting UTM parameters), but the impact zone is admin dashboard pages where charts render.

Know when Wp Statistics Simple Privacy Friendly Google Analytics Alternative gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

2
Analysis Updated
Apr 17, 2026 - 02:27 vuln.today
v2 - CVSS changed
CVE Published
Apr 17, 2026 - 01:24 nvd
HIGH 7.2

DescriptionCVE.org

The WP Statistics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'utm_source' parameter in all versions up to, and including, 14.16.4. This is due to insufficient input sanitization and output escaping. The plugin's referral parser copies the raw utm_source value into the source_name field when a wildcard channel domain matches, and the chart renderer later inserts this value into legend markup via innerHTML without escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in admin pages that will execute whenever an administrator accesses the Referrals Overview or Social Media analytics pages.

Executive ViewAI

Why It Matters

WP Statistics plugin versions 14.16.4 and earlier contain a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts into administrator dashboards, potentially compromising site management and enabling lateral attacks against WordPress administrators. Organizations using this plugin face immediate risk of administrative credential theft and site compromise without vendor patches available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable WP Statistics plugin immediately on all WordPress installations; (2) If plugin must remain active, restrict administrator access to trusted IP ranges via WAF or network controls; (3) Implement Content Security Policy (CSP) headers with strict script-src policies to limit XSS payload execution; (4) Monitor admin user login logs and dashboard access for anomalous behavior; (5) Conduct user access reviews to minimize number of accounts with admin privileges.

Threat Intelligence Overview

EPSS Score
0.1%
Top 77% exploitable
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

Related Vulnerabilities in WP Statistics Authorization and XSS Flaws

View all 2

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy