Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege Matomo account
-
DeliverySubmit crafted URL to SiteContentDetector/SitesManager
-
ExploitTrigger server-side request (SSRF)
-
ExecutionReach internal/metadata endpoint
-
ImpactExfiltrate limited sensitive information
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated session with at least low-privilege access to the Matomo administration interface (PR:L) and the ability to reach the SiteContentDetector/SitesManager functionality, which normally accepts a site URL for content detection - that URL-fetching feature is the exploitation surface. Limiting factors: exploitation is not possible against a fully anonymous attacker (valid credentials or an account are needed), there is no user interaction requirement, and impact is confined to limited information disclosure (C:L, no integrity or availability impact). Realistic risk is therefore highest for Matomo deployments that are internet-facing AND permit self-registration or grant low-trust users site-management capabilities; locked-down single-admin instances are substantially less exposed. |
| Impact | This is a moderate-severity SSRF (CWE-918) in Matomo 5.11.2 rated CVSS 5.0. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N indicates a network-reachable, low-complexity flaw requiring low-privilege authentication (PR:L), with a changed scope (S:C) but only limited confidentiality impact and no integrity or availability impact. SSVC aligns with this moderate picture: exploitation status is 'poc' (not active), automatable is 'no', and technical impact is 'partial' - meaning this is useful to a targeted attacker but not a mass-exploitation candidate. A public proof-of-concept exists (GitHub SLO-CYBER-SEC/CVE-2026-78850, corroborated by SSVC 'poc'), so weaponization effort is reduced, but there is NO CISA KEV listing and NO EPSS score was provided, so real-world exploitation probability cannot be quantified from the input. The signals are internally consistent - nothing contradicts the authenticated, information-disclosure-only reading. Net: a real but second-tier priority. It warrants patching on a normal cycle for internet-exposed Matomo instances, especially those allowing untrusted or low-trust user accounts, rather than emergency out-of-band response. Note the affected-version metadata is unreliable (CPE and EUVD both read 'n/a'), and no vendor security advisory was located in the references, so scope of affected versions is unconfirmed. |
| Exploit ScenarioDerived | An attacker with a low-privilege authenticated Matomo account (PR:L) sends a crafted request to the SiteContentDetector/SitesManager component, coercing the server to issue outbound requests to attacker-chosen URLs. Because scope is changed, the attacker can reach internal network resources or metadata endpoints normally shielded from the internet and read limited sensitive responses. A public proof-of-concept is available, lowering the skill required to reproduce the attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Server-side request forgery in Matomo 5.11.2 allows an attacker holding a low-privilege authenticated account to make the application issue HTTP requests to arbitrary destinations through the SiteContentDetector/SitesManager functionality, disclosing limited sensitive information from internal or otherwise unreachable services. The vulnerability is rated CVSS 5.0 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N) as a CWE-918 SSRF, so exploitation requires credentials but no user interaction, and impact is confined to confidentiality with no integrity or availability effect. Publicly available proof-of-concept code exists (SSVC exploitation status: poc; a dedicated CVE-2026-78850 demonstration repository is referenced), but there is no confirmed active exploitation (CISA KEV).
RemediationAI
No vendor-released patch version is identified in the available intelligence: the supplied references point to the Matomo repository and release tree (https://github.com/matomo-org/matomo, https://github.com/matomo-org/matomo/tree/5.11.2) and to the security advisories index (https://github.com/matomo-org/matomo/security/advisories), but none of them states a fixed version, so administrators should monitor that advisory index and the vendor site (https://matomo.org/) and apply the first release that explicitly lists CVE-2026-78850 as resolved before upgrading off 5.11.2. Until such a fix is confirmed, apply compensating controls targeted at the URL-fetching surface rather than generic hardening: restrict who can reach SitesManager and create or edit sites by removing site-management permissions from low-privilege and self-registered accounts (trade-off: legitimate delegated reporting workflows break until roles are re-scoped), and disable open self-registration on any internet-facing instance so an attacker cannot self-provision the PR:L foothold this issue requires (trade-off: public or community-facing Matomo deployments lose self-service onboarding). Because the flaw is SSRF, also constrain outbound network egress from the Matomo host with an allow-list that denies RFC1918 ranges, loopback, and cloud metadata endpoints such as 169.254.169.254, and block non-HTTP/HTTPS schemes at the egress layer (trade-off: legitimate off-site content detection and any internal integrations that rely on internal endpoints will fail and must be allow-listed explicitly). Where the content-detection feature is not operationally required, disable or avoid its URL-fetching path entirely, and note that the existence of a public proof-of-concept repository (https://github.com/SLO-CYBER-SEC/CVE-2026-78850) raises the likelihood of opportunistic attempts, so log and alert on outbound requests originating from Matomo to unexpected internal destinations.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
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-918 (Server-Side Request Forgery): Matomo's SiteContentDetector, used together with the SitesManager component, takes a site URL and performs server-side retrieval of that URL to detect the site's content management system and related metadata. Because the supplied URL is not adequately validated or restricted against internal address ranges and non-HTTP schemes, an attacker who can reach that URL-fetching feature can direct Matomo's own network position at targets the attacker cannot reach directly. The assessed CVSS vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N, meaning the attack is network-reachable with low complexity but requires a low-privileged authenticated session (PR:L), needs no user interaction, and has limited confidentiality impact only, though the scope change (S:C) reflects that the vulnerable component can affect resources beyond its own security authority. CPE data supplied with this CVE is unpopulated (all fields listed as n/a), and the EUVD affected-version field likewise records n/a, so the only firmly identified affected release is Matomo 5.11.2 as stated in the CVE description; the tags supplied are "SSRF" and "N A". Context matters here: the URL-fetching content-detection surface is the entire exploitation path, which is why deployments that grant site-management capability to low-trust or self-registered users are materially more exposed than locked-down single-admin instances.
Know when Matomo 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:L/UI:N/S:C/C:L/I:N/A:N
SSRF via a URL-fetch feature needs an authenticated low-privilege user (PR:L), is network-reachable with low complexity, crosses scope to internal systems (S:C), and leaks limited data (C:L only).
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
An issue in Matomo v.5.11.2 allows a remote attacker to obtain sensitive information via the SiteContentDetector / SitesManager component
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
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Directory traversal vulnerability in core/ViewDataTable/Factory.php in Piwik before 2.15.0 allows remote attackers to in
The DisplayTopKeywords function in plugins/Referrers/Controller.php in Piwik before 2.15.0 allows remote attackers to co
The official piwik Docker images before fpm-alpine (Alpine specific) contain a blank password for a root user. Rated cri
A full path disclosure vulnerability was discovered in Matomo v3.9.1 where a user can trigger a particular error to disc
The Matomo Analytics - Ethical Stats. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no a
The matomo_integration (aka Matomo Integration) extension before 1.3.2 for TYPO3 allows XSS. Rated medium severity (CVSS
Piwik before 1.11 accepts input from a POST request instead of a GET request in unspecified circumstances, which might a
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Piwik PRO a
Cross-site scripting (XSS) vulnerability in Piwik before 1.9 allows remote attackers to inject arbitrary web script or H
Cross-site scripting (XSS) vulnerability in Piwik before 1.11 allows remote attackers to inject arbitrary web script or
EUVD-2026-102185
GHSA-rw9v-xch6-cr33
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB