Matomo 2
Matomo 2
The Matomo 2 reached end of service life on Dec 18, 2017 — 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 2 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
- 2
- product Label
- Matomo
- release Label
- 2
- codename
- lts
- latest Version
- 2.18.1
- release Date
- 2013-12-17
- maintained
- source Url
- https://endoflife.date/matomo
Lifecycle Dates
- End of Service Life
- Dec 18, 2017
- Last OEM Support
- Dec 19, 2016
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Matomo 2 — 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 2?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Matomo 2 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 2 Support: Frequently Asked Questions
Is the Matomo 2 still supported?
Matomo ended support for the Matomo 2 on Dec 18, 2017 — 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 2 end of service life (EOSL) date?
Matomo lists the end of service life for the Matomo 2 as Dec 18, 2017.
Can I keep using the Matomo 2 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 2 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 2
3 published CVEs affect the Matomo 2, 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-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. |