How severe is CVE-2013-2633?

No CVSS score has been assigned to CVE-2013-2633 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-2633?

CVE-2013-2633 affects the following packages: matomo/matomo (Packagist), piwik/piwik (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-2633?

Update matomo/matomo to 1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2633 is resolved across your whole dependency graph.

How do I detect CVE-2013-2633 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matomo/matomo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-2633 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-2633 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-2633 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-2633?

CVE-2013-2633 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-2633?

CVE-2013-2633 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-2633 published, and has it been updated?

CVE-2013-2633 was published on May 13, 2022 and was last updated on April 12, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2013-2633 — matomo

CVE-2013-2633 is a Improper Input Validation vulnerability in matomo/matomo. A fix is available for matomo/matomo — see the affected versions and patch details below.

Piwik (now Matomo) Reveals Sensitive Information by Accepting Input from `POST` Requests

Published

May 13, 2022

Updated

Apr 12, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐘matomo/matomo🐘piwik/piwik

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`matomo/matomo`	all versions	1.11`composer require matomo/matomo:^1.11`
🐘Packagist	`piwik/piwik`	all versions	1.11`composer require piwik/piwik:^1.11`

Affected Products

1 product · 21 configurations

Application

matomomatomo

≤ 1.10.1

20 versions

1.01.11.1.11.21.2.11.31.41.51.5.11.61.71.7.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matomo/matomo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matomo/matomo to 1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2633 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-2633 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works