# CVE-2013-2633: Piwik (now Matomo) Reveals Sensitive Information by Accepting Input from `POST` Requests

> Attackers can obtain sensitive information by leveraging parameter logging when Piwik accepts POST input instead of GET.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v8h8-93mx-82h5

## What is CVE-2013-2633?

CVE-2013-2633 is a medium-severity vulnerability in n/a, published on 21 Mar 2013. It can be exploited over the network, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-2633?

4 open source packages ship an affected version, including matomo/matomo and piwik/piwik. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `matomo/matomo` | Packagist | All versions | 1.11 |
| `matomo/matomo` | Packagist | All versions | 1.11 |
| `piwik/piwik` | Packagist | All versions | 1.11 |
| `piwik/piwik` | Packagist | All versions | 1.11 |

Products: Matomo Matomo.

## How do I fix CVE-2013-2633?

Upgrade matomo/matomo to 1.11 or later.

## Is CVE-2013-2633 being exploited?

There is no known exploitation of CVE-2013-2633 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-7815](https://insights.sbomify.com/CVE-2015-7815/): Path traversal in n/a (high 7.5)
- [CVE-2015-7816](https://insights.sbomify.com/CVE-2015-7816/): Deserialization in n/a (high 7.5)
- [CVE-2009-4137](https://insights.sbomify.com/CVE-2009-4137/): Deserialization in n/a (high 7.5)
- [CVE-2009-4140](https://insights.sbomify.com/CVE-2009-4140/): File upload in n/a (high 7.5)
- [CVE-2011-4941](https://insights.sbomify.com/CVE-2011-4941/): Piwik (now Matomo) Vulnerable to Arbitrary Code Execution (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2633 and fix it if it is affected.

What it is: CVE-2013-2633 is a medium-severity vulnerability in n/a, published on 21 Mar 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2633 in the wild and no public exploit code.

Affected packages and fixed versions:
- matomo/matomo (Packagist): affected all versions; fixed in 1.11
- matomo/matomo (Packagist): affected all versions; fixed in 1.11
- piwik/piwik (Packagist): affected all versions; fixed in 1.11
- piwik/piwik (Packagist): affected all versions; fixed in 1.11

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2633/ (Markdown: https://insights.sbomify.com/CVE-2013-2633/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2633
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2633
- OSV: https://osv.dev/vulnerability/CVE-2013-2633

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2633/
Summaries are generated and may contain mistakes; the official description above is the record.