<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: coship</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2019-7564: An issue was discovered on Shenzhen Coship WM3300 WiFi Router 5.0.0.55 devices</title><link>https://patchthecve.com/cve/CVE-2019-7564.html</link><guid>https://patchthecve.com/cve/CVE-2019-7564.html</guid><pubDate>Wed, 17 Jun 2026 02:40:41 +0000</pubDate><description>CRITICAL 9.8: An issue was discovered on Shenzhen Coship WM3300 WiFi Router 5.0.0.55 devices. The password reset functionality of the Wireless SSID doesn&#x27;t require any type of authentication. By making a POST request to the regx/wireless/wl_security_2G.asp URI, the attacker can change the password of the Wi-FI ne</description></item><item><title>CVE-2019-6441: An issue was discovered on Shenzhen Coship RT3050 4.0.0.40, RT3052 4.0.0.48, RT7620 10.0.0.49, WM3300 5.0.0.54</title><link>https://patchthecve.com/cve/CVE-2019-6441.html</link><guid>https://patchthecve.com/cve/CVE-2019-6441.html</guid><pubDate>Wed, 17 Jun 2026 02:39:03 +0000</pubDate><description>CRITICAL 9.8: An issue was discovered on Shenzhen Coship RT3050 4.0.0.40, RT3052 4.0.0.48, RT7620 10.0.0.49, WM3300 5.0.0.54, and WM3300 5.0.0.55 devices. The password reset functionality of the router doesn&#x27;t have backend validation for the current password and doesn&#x27;t require any type of authentication. By maki</description></item><item><title>CVE-2018-8772: Coship RT3052 4.0.0.48 devices allow XSS via a crafted SSID field on the &quot;Wireless Setting - Basic&quot; screen.</title><link>https://patchthecve.com/cve/CVE-2018-8772.html</link><guid>https://patchthecve.com/cve/CVE-2018-8772.html</guid><pubDate>Wed, 17 Jun 2026 02:05:21 +0000</pubDate><description>MEDIUM 6.1: Coship RT3052 4.0.0.48 devices allow XSS via a crafted SSID field on the &quot;Wireless Setting - Basic&quot; screen.</description></item></channel></rss>