Overview 14 matches · 1 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
14matches
1in Waratek scope7.1%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
2public PoC14.3%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
7.1%
Outside Waratek scope
0
0.0%
Not applicable
13
92.9%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
14
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
14.3%
Proof of concept only
1
7.1%
Forecast only
0
0.0%
No public exploit
11
78.6%
split by
peak 6 / year
20091
Not applicable1
High1
not blocked1
Working exploit published1
20101
Not applicable1
High1
not blocked1
Working exploit published1
20110
20120
20130
20140
20150
20160
20170
20180
20193
No exploit published1
Not applicable2
High3
not blocked3
No public exploit3
20200
20210
20220
20236
Not applicable6
High6
not blocked6
No public exploit6
20242
Not applicable2
High2
not blocked2
No public exploit2
20251
Not applicable1
High1
not blocked1
Proof of concept only1
200920112013201520172019202120232025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-7197 | High | 2025-05-15 | Not applicable | Proof of concept only | The Marketing Twitter Bot WordPress plugin through 1.11 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack |
| CVE-2024-49685 | High | 2024-10-31 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) vulnerability in Syed Balkhi Custom Twitter Feeds (Tweets Widget) custom-twitter-feeds allows Cross Site Request Forgery.This issue affects Custom Twitter Feeds (Tweets Widget): from n/a through <= 2.2.3. |
| CVE-2023-52136 | High | 2024-01-05 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) vulnerability in Smash Balloon Custom Twitter Feeds – A Tweets Widget or X Feed Widget.This issue affects Custom Twitter Feeds – A Tweets Widget or X Feed Widget: from n/a through 2.1.2. |
| CVE-2023-34384 | High | 2023-11-13 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) vulnerability in Kebo Kebo Twitter Feed plugin <= 1.5.12 versions. |
| CVE-2023-5709 | High | 2023-11-07 | Not applicable | No public exploit | The WD WidgetTwitter plugin for WordPress is vulnerable to SQL Injection via the plugin's shortcode in versions up to, and including, 1.0.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers with contributor-level and above permissions to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. |
| CVE-2012-10015 | High | 2023-05-31 | Not applicable | No public exploit | 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-2022-33974 | High | 2023-05-29 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) vulnerability in Smash Balloon Custom Twitter Feeds (Tweets Widget) plugin <= 1.8.4 versions. |
| CVE-2023-23706 | High | 2023-05-23 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) vulnerability in miniOrange WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn) plugin <= 7.5.14 versions. |
| CVE-2015-10096 | High | 2023-03-20 | Not applicable | No public exploit | A vulnerability, which was classified as critical, was found in Zarthus IRC Twitter Announcer Bot up to 1.1.0. This affects the function get_tweets of the file lib/twitterbot/plugins/twitter_announcer.rb. The manipulation of the argument tweet leads to command injection. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. Upgrading to version 1.1.1 is able to address this issue. The patch is named 6b1941b7fc2c70e1f40981b43c84a2c20cc12bd3. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-223383. |
| CVE-2019-16263 | High | 2019-10-07 | Not applicable | No public exploit | The Twitter Kit framework through 3.4.2 for iOS does not properly validate the api.twitter.com SSL certificate. Although the certificate chain must contain one of a set of pinned certificates, there are certain implementation errors such as a lack of hostname verification. NOTE: this is an end-of-life product. |
| CVE-2017-18504 | High | 2019-08-12 | Not applicable | No public exploit | The twitter-cards-meta plugin before 2.5.0 for WordPress has CSRF. |
| CVE-2019-10313 | High | 2019-04-30 | No exploit published | No public exploit | Jenkins Twitter Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system. |
| CVE-2010-1983 | High | 2010-05-19 | Not applicable | Working exploit published | Directory traversal vulnerability in the redTWITTER (com_redtwitter) component 1.0.x including 1.0b11 for Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the view parameter to index.php. NOTE: some of these details are obtained from third party information. |
| CVE-2008-7083 | High | 2009-08-25 | Not applicable | Working exploit published | Multiple SQL injection vulnerabilities in ReVou Micro Blogging Twitter clone allow remote attackers to execute arbitrary SQL commands via the (1) username and (2) password fields. |