Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

tweetscribe vulnerabilities and fixes

Recent CVEs affecting tweetscribe, with upgrade or downgrade steps. 1 tracked.

tweetscribe has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-12-31. Highest priority: CVE-2014-9399 (score 45/100).

FAQ

How do I fix tweetscribe 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 tweetscribe being exploited right now?

None of the tracked tweetscribe CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which tweetscribe CVE should I patch first?

CVE-2014-9399 currently ranks highest (45/100): Cross-site request forgery (CSRF) vulnerability in the TweetScribe plugin 1.1 and earlier for WordPress allows.

← Back to latest CVEs