zh yandexmap vulnerabilities and fixes
Recent CVEs affecting zh yandexmap, with upgrade or downgrade steps. 2 tracked.
Also searched as: zhyandexmap.
zh yandexmap has 2 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-02-05. Highest priority: CVE-2017-15966 (score 67/100).
- CVE-2018-6604 CRITICAL 9.8 DOWNGRADE SQL Injection exists in the Zh YandexMap 6.2.1.0 component for Joomla! via the id parameter in a task=getPlace
- CVE-2017-15966 CRITICAL 9.8 DOWNGRADE The Zh YandexMap (aka com_zhyandexmap) component 6.1.1.0 for Joomla! allows SQL Injection via the placemarklis
FAQ
How do I fix zh yandexmap vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is zh yandexmap being exploited right now?
None of the tracked zh yandexmap CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which zh yandexmap CVE should I patch first?
CVE-2017-15966 currently ranks highest (67/100): The Zh YandexMap (aka com_zhyandexmap) component 6.1.1.0 for Joomla! allows SQL Injection via the placemarklis.