PatchTheCVEmywebsql vulnerabilities and fixes
Recent CVEs affecting mywebsql, with upgrade or downgrade steps. 4 tracked.
mywebsql has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-02-11. Highest priority: CVE-2019-7731 (score 67/100).
- CVE-2019-7731 CRITICAL 9.8 DOWNGRADE MyWebSQL 3.7 has a remote code execution (RCE) vulnerability after an attacker writes shell code into the data
- CVE-2019-7730 MEDIUM 5.7 DOWNGRADE MyWebSQL 3.7 has a Cross-site request forgery (CSRF) vulnerability for deleting a database via the /?q=wrkfrm&
- CVE-2019-7544 MEDIUM 5.4 UPGRADE An issue was discovered in MyWebSQL 3.7
- CVE-2017-1000011 MEDIUM 6.1 DOWNGRADE MyWebSQL version 3.6 is vulnerable to stored XSS in the database manager component resulting in account takeov
FAQ
How do I fix mywebsql 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 mywebsql being exploited right now?
None of the tracked mywebsql CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mywebsql CVE should I patch first?
CVE-2019-7731 currently ranks highest (67/100): MyWebSQL 3.7 has a remote code execution (RCE) vulnerability after an attacker writes shell code into the data.