Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted Web Vitals metric
-
DeliveryPayload stored unsanitized in plugin data
-
ExploitAdmin opens reporting page
-
ExecutionScript executes in admin browser
-
ImpactHijack admin session / create rogue admin
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 target site to be running the Web Vitals Tracking plugin (version through 5.4.2) with its unauthenticated visitor-side performance-measurement submission endpoint reachable - the plugin stores visitor-supplied metrics and renders them in a script context on an administrative page without validation or escaping. No attacker authentication is needed (PR:N). The key limiting factor is UI:R: the payload only fires when a logged-in administrator views the affected admin reporting page, so exploitation is contingent on admin activity rather than firing automatically. There is no indication of a non-default configuration requirement; the stored-and-rendered behavior appears inherent to the plugin. |
| Impact | Signals are moderately aligned toward a credible but not top-tier priority. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R) correctly captures a remotely reachable, unauthenticated, low-complexity injection that nonetheless requires victim interaction - specifically an administrator viewing the affected admin page - which is why UI:R is present. Publicly available exploit code exists (WPScan), raising the practical likelihood of opportunistic use, but there is NO CISA KEV listing and NO EPSS score was provided in the input, so widespread automated exploitation cannot be confirmed from the data. The NVD C:H/I:H/A:H impact rating (driving the 8.8) is debatable for a stored-XSS/CWE-79 issue: raw XSS confidentiality/integrity impact is typically Low, and the High rating appears to assume full administrator-session takeover leading to site compromise - plausible in WordPress (admin JS can create rogue admins or abuse the plugin/theme editor for code execution) but an inference rather than a directly demonstrated impact. Net: a real, patch-worthy vulnerability whose true risk hinges on the UI:R requirement and the admin-escalation assumption; treat as elevated for exposed WordPress sites running this plugin, but not as an actively-exploited emergency absent KEV/EPSS evidence. |
| Exploit ScenarioDerived | An unauthenticated visitor submits crafted performance-measurement data containing a malicious script payload to the Web Vitals Tracking plugin, which stores it without validation or escaping. When a logged-in administrator later opens the plugin's reporting page in wp-admin, the payload executes in a script context in their browser, letting the attacker act with the admin's privileges (e.g., create a rogue admin account or inject site code). Public exploit code for this flaw is available via WPScan, lowering the barrier to reproduction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Stored cross-site scripting in the WordPress plugin Web Vitals Tracking (versions through 5.4.2) allows unauthenticated visitors to inject arbitrary script content by submitting unvalidated, unescaped performance measurements that the plugin persists and later renders inside a script context on an administrative reporting page. The attack is remote and unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R), but the payload only executes when a logged-in administrator loads the affected admin page, so exploitation depends on administrator activity rather than firing automatically; publicly available exploit code exists and the issue is tracked by WPScan as well as EUVD-2026-96769. Our independent assessment rates the impact more conservatively than the vendor/NVD score (scope-changed XSS with low confidentiality and integrity impact and no availability impact), so this should be treated as a credible, medium-to-high priority issue rather than a top-tier emergency.
RemediationAI
No vendor-released patch is identified in the available intelligence at time of analysis - the affected range simply runs "through 5.4.2" with no fixed version published - so the primary action is to confirm whether a patched release has since appeared in the WordPress plugin repository and, in the interim, deactivate or remove the Web Vitals Tracking plugin from any site that does not strictly need it, which is the only complete fix but costs you the plugin's performance-metrics functionality. If the plugin must remain active, treat this as a containment problem: block or heavily rate-limit the public performance-metrics submission endpoint (for example at the reverse proxy/WAF or by restricting POSTs to the plugin's collection path), accepting that this will disable legitimate visitor metrics; tighten access to the administrative reporting page so only trusted, fully patched administrator accounts can view it, and enforce re-authentication or IP allow-listing for wp-admin as a trade-off in admin convenience; and deploy a Content-Security-Policy that disallows inline script execution on admin pages, which mitigates script-context injection vectors generically but can break other plugins relying on inline scripts. Because the request is unauthenticated and the payload is stored, also audit the plugin's stored metric table for previously injected values before rebuilding the page, since simply updating or removing code does not clean already-persisted payloads. Track the vendor advisory and WPScan entry (https://wpscan.com/vulnerability/c6250c43-42c5-4c76-9eb9-2b35ba461e8c/) for the release of a patched version and patch as soon as one is confirmed; no exact fix version can be cited from the data provided.
Affected VersionsENISA
Affected Packages
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
The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e., cross-site scripting) in its stored variant, within a WordPress plugin that collects Core Web Vitals style performance metrics from anonymous site visitors. Because the plugin neither validates nor escapes the submitted measurement values before writing them to the database and then emits them into a script context on an administrative dashboard/reporting page, an attacker can break out of the intended JavaScript string or data structure (for example by injecting quote, tag, or script-terminator sequences into a metric field) and have arbitrary JavaScript parsed as part of the admin page - a classic stored XSS leading to script-context injection. The CPE string cpe:2.3:a:unknown:web_vitals_tracking:*:*:*:*:*:*:*:* reflects that the vendor/product mapping is not yet normalized in NVD, while EUVD records the affected range as Web Vitals Tracking 0 through 5.4.2. Our assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) differs from the 8.8 vendor/NVD vector chiefly in treating the compromise as scope-changing with limited confidentiality/integrity impact and no availability impact, and it confirms PR:N (unauthenticated submission) with UI:R (administrator must view the injected page).
Know when Web Vitals Tracking 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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Unauthenticated remote injection (PR:N, AV:N) but needs an admin to view the page (UI:R); XSS executes in a different context (S:C) with Low C/I and no availability impact, though admin-session abuse could escalate.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Web Vitals Tracking WordPress plugin through 5.4.2 does not validate or escape performance measurements submitted by unauthenticated visitors before storing them and outputting them in a script context on an administrative page, allowing unauthenticated attackers to perform Stored Cross-Site Scripting attacks against administrators.
Technical POC Analysis
Evidence caveat up front: the only supplied source is the WPScan advisory.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The WordPress plugin Web Vitals Tracking, in all versions through 5.4.2, carries a stored cross-site scripting vulnerability (CVE-2026-87760) for which no vendor patch has been released and publicly available exploit code exists. An unauthenticated attacker can plant malicious script that fires in the browser of any logged-in administrator who opens the plugin's reporting page, potentially handing over administrative sessions and with them control of site content, plugins, and collected visitor data. Because this plugin sits on internet-facing WordPress estates and remediation depends on a vendor fix that does not yet exist, leadership should treat it as an actionable exposure requiring near-term containment rather than routine patch-cycle handling.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or uninstall Web Vitals Tracking on affected instances (through 5.4.2) where it is not essential; restrict the plugin's administrative reporting page to a minimal, trusted set of administrators; enforce MFA and unique credentials for all WordPress administrators and avoid browsing untrusted content while logged in as admin; deploy WAF or virtual patching rules that reject script markup in performance-measurement submission fields; monitor logs for injected payloads and treat any detected injection as an administrative session compromise requiring credential and salt rotation.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-96769
GHSA-pwvc-4967-h5ch
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB