HomeWordPress vulnerabilitiesTwitter
Twitter vulnerabilities
Twitter has 2 known vulnerabilities in this database. The most recent published record is dated 31 May 2023.
- Known vulnerabilities
- 2
- Active installs
- 9,000+
- Latest version
- 2.0.5
- Last updated
- 24 Jul 2019
- Most recent
- 31 May 2023
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2014-125103 | Low 2.4 | Up to 1.3.2 | Fixed in a later version (latest 2.0.5) | 31 May 2023 |
| Cross-site request forgery (CSRF) CVE-2012-10015 | Medium 4.3 | Before 2.15 | Fixed in 2.15 | 31 May 2023 |
Read the published descriptions
- CVE-2014-125103, 31 May 2023
- A vulnerability was found in BestWebSoft Twitter Plugin up to 1.3.2 on WordPress. It has been declared as problematic. Affected by this vulnerability is the function twttr_settings_page of the file twitter.php. The manipulation of the argument twttr_url_twitter/bws_license_key/bws_license_plugin leads to cross site scripting. The attack can be launched remotely. Upgrading to version 1.3.7 is able to address this issue. The patch is named e04d59ab578316ffeb204cf32dc71c0d0e1ff77c. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-230155. CVE record
- CVE-2012-10015, 31 May 2023
- A vulnerability was found in BestWebSoft Twitter Plugin up to 2.14 on WordPress. It has been classified as problematic. Affected is the function twttr_settings_page of the file twitter.php of the component Settings Page. The manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. Upgrading to version 2.15 is able to address this issue. The patch is identified as a6d4659cbb2cbf18ccb0fb43549d5113d74e0146. It is recommended to upgrade the affected component. VDB-230154 is the identifier assigned to this vulnerability. CVE record
What to do if you run Twitter
If you run Twitter, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Twitter vulnerabilities
Free. We email you when a new vulnerability is published for Twitter, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.