Overview 10 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 EPSS ≥ 0.5
10matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
10
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
10
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
10
100.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 2 / year
20001
Not applicable1
Low1
not blocked1
Working exploit published1
20010
20020
20030
20040
20050
20061
Not applicable1
Medium1
not blocked1
Working exploit published1
20072
Not applicable2
High1
Medium1
not blocked2
Working exploit published2
20080
20090
20100
20110
20120
20130
20140
20150
20160
20170
20180
20192
Not applicable2
Critical1
High1
not blocked2
Working exploit published2
20200
20210
20221
Not applicable1
Critical1
not blocked1
Working exploit published1
20232
Not applicable2
Critical1
Medium1
not blocked2
Working exploit published2
20241
Not applicable1
Critical1
not blocked1
Working exploit published1
2000200220042006200820102012201420162018202020222024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-9989 | Critical | 2024-10-29 | Not applicable | Working exploit published | The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.18. This is due to a limited arbitrary method call to 'crypto_connect_ajax_process::log_in' function in the 'crypto_connect_ajax_process' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the username. |
| CVE-2023-37759 | Critical | 2023-09-08 | Not applicable | Working exploit published | Incorrect access control in the User Registration page of Crypto Currency Tracker (CCT) before v9.5 allows unauthenticated attackers to register as an Admin account via a crafted POST request. |
| CVE-2023-1546 | Medium | 2023-05-02 | Not applicable | Working exploit published | The MyCryptoCheckout WordPress plugin before 2.124 does not escape some URLs before outputting them in attributes, leading to Reflected Cross-Site Scripting |
| CVE-2022-44588 | Critical | 2022-12-15 | Not applicable | Working exploit published | Unauth. SQL Injection vulnerability in Cryptocurrency Widgets Pack Plugin <=1.8.1 on WordPress. |
| CVE-2013-4103 | Critical | 2019-11-04 | Not applicable | Working exploit published | Cryptocat before 2.0.22 has Remote Script Injection due to improperly sanitizing user input |
| CVE-2013-2261 | High | 2019-11-04 | Not applicable | Working exploit published | Cryptocat before 2.0.22 Chrome Extension 'img/keygen.gif' has Information Disclosure |
| CVE-2007-4903 | High | 2007-09-17 | Not applicable | Working exploit published | Multiple buffer overflows in a certain ActiveX control in CryptoX.dll 2.0 and earlier in the Ultra Crypto Component allow remote attackers to execute arbitrary code via (1) a long string in the first argument to the AcquireContext method or (2) an unspecified vector to the DeleteContext method. |
| CVE-2007-4902 | Medium | 2007-09-17 | Not applicable | Working exploit published | Absolute path traversal vulnerability in a certain ActiveX control in CryptoX.dll 2.0 and earlier in the Ultra Crypto Component allows remote attackers to write to arbitrary files via a full pathname in the argument to the SaveToFile method. |
| CVE-2006-1172 | Medium | 2006-05-09 | Not applicable | Working exploit published | Stack-based buffer overflow in the createPKCS10 function in Cryptomathic Cenroll ActiveX Control 1.1.0.0 allows remote attackers to execute arbitrary code via vectors related to the TDC Digital signature. |
| CVE-2000-0275 | Low | 2000-04-10 | Not applicable | Working exploit published | CRYPTOCard CryptoAdmin for PalmOS uses weak encryption to store a user's PIN number, which allows an attacker with access to the .PDB file to generate valid PT-1 tokens after cracking the PIN. |