What is CVE-2017-20175?

CVE-2017-20175 is a medium-severity cross-site scripting (XSS) vulnerability in mediawiki/matomo (composer), affecting versions < 2.4.3. It is fixed in 2.4.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2017-20175?

CVE-2017-20175 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of mediawiki/matomo are affected by CVE-2017-20175?

mediawiki/matomo (composer) versions < 2.4.3 is affected.

Is there a fix for CVE-2017-20175?

Yes. CVE-2017-20175 is fixed in 2.4.3. Upgrade to this version or later.

Is CVE-2017-20175 exploitable, and should I be worried?

Whether CVE-2017-20175 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-20175 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-20175 in mediawiki/matomo

Q: How severe is CVE-2017-20175?

CVE-2017-20175 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of mediawiki/matomo are affected by CVE-2017-20175?

mediawiki/matomo (composer) versions < 2.4.3 is affected.

Q: Is there a fix for CVE-2017-20175?

Yes. CVE-2017-20175 is fixed in 2.4.3. Upgrade to this version or later.

Q: Is CVE-2017-20175 exploitable, and should I be worried?

Whether CVE-2017-20175 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-20175 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-20175?

Upgrade mediawiki/matomo to 2.4.3 or later.

Summary

Cross-site Scripting in DaSchTour matomo-mediawiki-extension

A vulnerability classified as problematic has been found in DaSchTour matomo-mediawiki-extension up to 2.4.2. This affects an unknown part of the file Piwik.hooks.php of the component Username Handler. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.4.3 is able to address this issue. The name of the patch is 681324e4f518a8af4bd1f93867074c728eb9923d. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-220203.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2017-20175 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.4.3); upgrading removes the vulnerable code path.

Affected versions

mediawiki/matomo (< 2.4.3)

Security releases

mediawiki/matomo → 2.4.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade mediawiki/matomo to 2.4.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-20175? CVE-2017-20175 is a medium-severity cross-site scripting (XSS) vulnerability in mediawiki/matomo (composer), affecting versions < 2.4.3. It is fixed in 2.4.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2017-20175? CVE-2017-20175 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of mediawiki/matomo are affected by CVE-2017-20175? mediawiki/matomo (composer) versions < 2.4.3 is affected.
Is there a fix for CVE-2017-20175? Yes. CVE-2017-20175 is fixed in 2.4.3. Upgrade to this version or later.
Is CVE-2017-20175 exploitable, and should I be worried? Whether CVE-2017-20175 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-20175 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-20175? Upgrade mediawiki/matomo to 2.4.3 or later.