PatchTheCVEtwitget vulnerabilities and fixes
Recent CVEs affecting twitget, with upgrade or downgrade steps. 2 tracked.
twitget has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2014-10-17. Highest priority: CVE-2014-2559 (score 51/100).
- CVE-2014-2995 LOW 3.5 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in twitget.php in the Twitget plugin before 3.3.3 for Word
- CVE-2014-2559 MEDIUM 6.8 UPGRADE Multiple cross-site request forgery (CSRF) vulnerabilities in twitget.php in the Twitget plugin before 3.3.3 f
FAQ
How do I fix twitget 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 twitget being exploited right now?
None of the tracked twitget CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which twitget CVE should I patch first?
CVE-2014-2559 currently ranks highest (51/100): Multiple cross-site request forgery (CSRF) vulnerabilities in twitget.php in the Twitget plugin before 3.3.3 f.