Matomo 1
Matomo 1
The Matomo 1 reached end of service life on Dec 17, 2013 — Matomo no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Matomo 1 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- matomo
- release
- 1
- product Label
- Matomo
- release Label
- 1
- codename
- lts
- latest Version
- 1.12
- release Date
- 2010-08-28
- maintained
- source Url
- https://endoflife.date/matomo
Lifecycle Dates
- End of Service Life
- Dec 17, 2013
- Last OEM Support
- Dec 17, 2013
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Matomo 1 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Matomo 1?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Matomo 1 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Matomo 1 Support: Frequently Asked Questions
Is the Matomo 1 still supported?
Matomo ended support for the Matomo 1 on Dec 17, 2013 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Matomo 1 end of service life (EOSL) date?
Matomo lists the end of service life for the Matomo 1 as Dec 17, 2013.
Can I keep using the Matomo 1 after its EOSL date?
Yes. EOSL means Matomo stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Matomo 1 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Matomo 1
16 published CVEs affect the Matomo 1, including 2 rated critical or high severity. Matomo no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2015-7816 | HIGH | 7.5 | Nov 16, 2015 | The DisplayTopKeywords function in plugins/Referrers/Controller.php in Piwik before 2.15.0 allows remote attackers to conduct PHP object injection attacks, conduct Server-Side Request Forgery (SSRF) attacks, and execute arbitrary PHP code via a crafted HTTP header. |
| CVE-2015-7815 | HIGH | 7.5 | Nov 16, 2015 | Directory traversal vulnerability in core/ViewDataTable/Factory.php in Piwik before 2.15.0 allows remote attackers to include and execute arbitrary local files via the viewDataTable parameter. |
| CVE-2011-4941 | MEDIUM | 6.8 | Sep 18, 2012 | Unspecified vulnerability in Piwik 1.2 through 1.4 allows remote attackers with the view permission to execute arbitrary code via unknown attack vectors. |
| CVE-2011-0398 | MEDIUM | 6.4 | Jan 10, 2011 | The Piwik_Common::getIP function in Piwik before 1.1 does not properly determine the client IP address, which allows remote attackers to bypass intended geolocation and logging functionality via (1) use of a private (aka RFC 1918) address behind a proxy server or (2) spoofing of the X-Forwarded-For HTTP header. |
| CVE-2023-6923 | MEDIUM | 6.1 | Feb 29, 2024 | The Matomo Analytics – Ethical Stats. Powerful Insights. plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the idsite parameter in all versions up to, and including, 4.15.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2013-0195 | MEDIUM | 6.1 | Nov 20, 2019 | Cross-site Scripting (XSS) in Piwik before 1.10.1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. NOTE: This is a different vulnerability than CVE-2013-0193 and CVE-2013-0194. |
| CVE-2013-0194 | MEDIUM | 6.1 | Nov 20, 2019 | Cross-site Scripting (XSS) in Piwik before 1.10.1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. NOTE: This is a different vulnerability than CVE-2013-0193 and CVE-2013-0195. |
| CVE-2013-0193 | MEDIUM | 6.1 | Nov 20, 2019 | Cross-site Scripting (XSS) in Piwik before 1.10.1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. NOTE: This is a different vulnerability than CVE-2013-0194 and CVE-2013-0195. |
| CVE-2013-2633 | MEDIUM | 5.0 | Mar 21, 2013 | Piwik before 1.11 accepts input from a POST request instead of a GET request in unspecified circumstances, which might allow attackers to obtain sensitive information by leveraging the logging of parameters. |
| CVE-2011-3791 | MEDIUM | 5.0 | Sep 24, 2011 | Piwik 1.1 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by plugins/Widgetize/Widgetize.php and certain other files. |
| CVE-2011-0401 | MEDIUM | 5.0 | Jan 10, 2011 | Piwik before 1.1 does not properly limit the number of files stored under tmp/sessions/, which might allow remote attackers to cause a denial of service (inode consumption) by establishing many sessions. |
| CVE-2011-0400 | MEDIUM | 5.0 | Jan 10, 2011 | Cookie.php in Piwik before 1.1 does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session. |
| CVE-2013-1844 | MEDIUM | 4.3 | Mar 21, 2013 | Cross-site scripting (XSS) vulnerability in Piwik before 1.11 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. |
| CVE-2012-4541 | MEDIUM | 4.3 | Nov 19, 2012 | Cross-site scripting (XSS) vulnerability in Piwik before 1.9 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. |
| CVE-2011-0399 | MEDIUM | 4.3 | Jan 10, 2011 | Piwik before 1.1 does not prevent the rendering of the login form inside a frame in a third-party HTML document, which makes it easier for remote attackers to conduct clickjacking attacks via a crafted web site. |
| CVE-2011-0004 | MEDIUM | 4.3 | Jan 10, 2011 | Multiple cross-site scripting (XSS) vulnerabilities in Piwik before 1.1 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors. |