Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Unauthenticated network stored XSS (AV:N/AC:L/PR:N) needs a victim admin to view the payload (UI:R), and script executing in the admin's context crosses into the Joomla site (S:C) enabling takeover-level C/I/A impact.
Primary rating from Vendor (Joomla).
CVSS VectorVendor: Joomla
Lifecycle Timeline
2DescriptionCVE.org
The Joomla extension 4Analytics is vulnerable to an unauthenticated stored XSS. A specially crafted unauthenticated request may result in website takeover under some circumstances.
AnalysisAI
Unauthenticated stored cross-site scripting in the 4Analytics analytics extension for Joomla (by weeblr.com) lets a remote attacker inject persistent JavaScript through a specially crafted request, with no login required. Because the payload is stored and later rendered in a privileged context, it can escalate to full website takeover under some conditions. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.
Technical ContextAI
The affected component is the 4Analytics extension (cpe:2.3:a:weeblr.com:4analytics_extension_for_joomla), a third-party privacy-focused web analytics add-on that runs inside the Joomla CMS. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), meaning attacker-supplied data reaching the extension - plausibly analytics/tracking parameters captured from unauthenticated visitors - is persisted and later echoed into an HTML context without adequate output encoding. Stored XSS in analytics tooling is especially dangerous because the injected data is frequently rendered back inside an administrator-facing dashboard, executing attacker script in the browser of a logged-in Joomla admin.
RemediationAI
No vendor-released patch version was identified at time of analysis, and no advisory URL beyond the product page (https://weeblr.com/joomla-seo/4analytics-private-analytics-for-joomla) was provided, so administrators should monitor weeblr.com for an updated 4Analytics release and apply it as soon as it ships. As compensating controls until a fix is confirmed: consider disabling or uninstalling the 4Analytics extension if analytics collection is non-essential (trade-off: loss of visitor analytics); place a Web Application Firewall rule in front of Joomla to filter script-bearing payloads (<script, event handlers, javascript:) on the endpoints 4Analytics uses to ingest tracking data (trade-off: possible false positives on legitimate requests); and restrict administrator dashboard access to trusted IP ranges so a stored payload is less likely to render in an admin session (trade-off: operational friction for remote admins). Enforce a strict Content-Security-Policy that disallows inline script as a browser-side mitigation against payload execution.
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-44602
GHSA-xh64-rxr5-8ggh