How severe is CVE-2022-33156?

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

Which packages are affected by CVE-2022-33156?

CVE-2022-33156 affects the following packages: matomo (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2022-33156?

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

How do I detect CVE-2022-33156 in my Bitnami dependencies?

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

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2022-33156 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-33156 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-2022-33156?

CVE-2022-33156 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th 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-2022-33156?

CVE-2022-33156 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-33156 published, and has it been updated?

CVE-2022-33156 was published on March 6, 2024 and was last updated on April 3, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2022-33156 — matomo

CVE-2022-33156 is a Cross-site Scripting (XSS) vulnerability in matomo. A fix is available for matomo — see the affected versions and patch details below.

Also known asGHSA-gvxv-p9rv-gmcg

Published

Mar 6, 2024

Updated

Apr 3, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

📦matomo

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

Description

The matomo_integration (aka Matomo Integration) extension before 1.3.2 for TYPO3 allows XSS.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`matomo`	all versions	1.3.2

Affected Products

1 product · 1 configurations

Application

integrationmatomo

< 1.3.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matomo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matomo to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-33156 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

The matomo_integration (aka Matomo Integration) extension before 1.3.2 for TYPO3 allows XSS.

O3 Security · Impact-Aware SCA

Is CVE-2022-33156 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works