CVE-2017-20175
2.6 · LOWOverview
CVE-2017-20175 is a low-severity vulnerability affecting mediawiki matomo. It was published on February 5, 2023 and has a CVSS 3.1 base score of 2.6 (LOW).
This vulnerability has a CVSS 3.1 base score of 2.6, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
Technical Description
A vulnerability classified as problematic has been found in DaSchTour matomo-mediawiki-extension up to 2.4.2 on MediaWiki. 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 complexity of an attack is rather high. The exploitability is told to be difficult. 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 patch is named 681324e4f518a8af4bd1f93867074c728eb9923d. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-220203.
Remediation
Check the references section for vendor advisories and patches from mediawiki. Update matomo to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| mediawiki | matomo | >= 2.4.0, < 2.4.3 | Affected |
References
Frequently Asked Questions
What is CVE-2017-20175?
CVE-2017-20175 is a low-severity vulnerability affecting mediawiki matomo. It was published on February 5, 2023 and has a CVSS 3.1 base score of 2.6 (LOW).
How severe is CVE-2017-20175?
This vulnerability has a CVSS 3.1 base score of 2.6, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2017-20175?
Check the references section for vendor advisories and patches from mediawiki. Update matomo to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2017-20175?
CyberStrike's AI-powered security agents can automatically detect CVE-2017-20175 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2017
View all →The BIOS in Intel Compute Stick systems based on 6th Gen Intel Core processors prior to version CC04
The BIOS in Intel NUC systems based on 6th Gen Intel Core processors prior to version KY0045 may all
The BIOS in Intel NUC systems based on 6th Gen Intel Core processors prior to version SY0059 may all
Xen PV guest before Xen 4.3 checked access permissions to MMIO ranges only after accessing them, all
Airwatch Inbox for Android contains a vulnerability that may allow a rooted device to decrypt the lo
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: InnoDB). Supporte
In BlackBerry QNX Software Development Platform (SDP) 6.6.0, an information disclosure vulnerability
In BlackBerry QNX Software Development Platform (SDP) 6.6.0 and 6.5.0 SP1 and earlier, an informatio
Dotclear before 2.10.3, when the Host header is not part of the web server routing process, allows r
A directory traversal exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT
Clustered Data ONTAP versions 8.0, 8.3.1, and 8.3.2 contain a default privileged account which under
Versions 1.17 and 1.18 of the Python urllib3 library suffer from a vulnerability that can cause them