Overview 12 matches · 4 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 2 EPSS ≥ 0.5
12matches
4in Waratek scope33.3%
2protected16.7%
0exploited0.0%
0CISA KEV0.0%
2public PoC16.7%
2EPSS ≥ 0.516.7%
Protected by Waratek
2
16.7%
Rule in development
0
0.0%
Mitigation candidate
1
8.3%
No exploit published
1
8.3%
Outside Waratek scope
0
0.0%
Not applicable
8
66.7%
Withdrawn CVE
0
0.0%
blocked by ARMR today
2
16.7%
partly blocked
0
0.0%
not blocked
10
83.3%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
12
100.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 5 / year
20181
Protected by Waratek1
Critical1
blocked by ARMR today1
Proof of concept only1
20190
20201
Mitigation candidate1
High1
not blocked1
Proof of concept only1
20210
20223
Not applicable3
High1
Medium2
not blocked3
Proof of concept only3
20235
Protected by Waratek1
No exploit published1
Not applicable3
Critical1
High2
Medium2
blocked by ARMR today1
not blocked4
Proof of concept only5
20240
20252
Not applicable2
Low2
not blocked2
Proof of concept only2
20182019202020212022202320242025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-13123 | Low | 2025-03-25 | Not applicable | Proof of concept only | The AFI WordPress plugin before 1.100.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). |
| CVE-2024-13122 | Low | 2025-03-25 | Not applicable | Proof of concept only | The AFI WordPress plugin before 1.100.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). |
| CVE-2022-4244 | High | 2023-09-25 | Protected by Waratek | Proof of concept only | A flaw was found in codeplex-codehaus. A directory traversal attack (also known as path traversal) aims to access files and directories stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and their variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on the file system, including application source code, configuration, and other critical system files. |
| CVE-2023-2527 | Medium | 2023-06-19 | Not applicable | Proof of concept only | The Integration for Contact Form 7 and Zoho CRM, Bigin WordPress plugin before 1.2.4 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin |
| CVE-2023-0812 | High | 2023-05-15 | Not applicable | Proof of concept only | The Active Directory Integration / LDAP Integration WordPress plugin before 4.1.1 does not have proper authorization or nonce values for some POST requests, leading to unauthenticated data disclosure. |
| CVE-2022-4426 | Medium | 2023-01-09 | Not applicable | Proof of concept only | The Mautic Integration for WooCommerce WordPress plugin before 1.0.3 does not have proper CSRF check when updating settings, and does not ensure that the options to be updated belong to the plugin, allowing attackers to make a logged in admin change arbitrary blog options via a CSRF attack. |
| CVE-2023-22457 | Critical | 2023-01-04 | No exploit published | Proof of concept only | CKEditor Integration UI adds support for editing wiki pages using CKEditor. Prior to versions 1.64.3,t he `CKEditor.HTMLConverter` document lacked a protection against Cross-Site Request Forgery (CSRF), allowing to execute macros with the rights of the current user. If a privileged user with programming rights was tricked into executing a GET request to this document with certain parameters (e.g., via an image with a corresponding URL embedded in a comment or via a redirect), this would allow arbitrary remote code execution and the attacker could gain rights, access private information or impact the availability of the wiki. The issue has been patched in the CKEditor Integration version 1.64.3. This has also been patched in the version of the CKEditor integration that is bundled starting with XWiki 14.6 RC1. There are no known workarounds for this other than upgrading the CKEditor integration to a fixed version. |
| CVE-2022-3420 | Medium | 2022-10-31 | Not applicable | Proof of concept only | The Official Integration for Billingo WordPress plugin before 3.4.0 does not sanitise and escape some of its settings, which could allow high privilege users with a role as low as Shop Manager to perform Stored Cross-Site Scripting attacks. |
| CVE-2022-3082 | Medium | 2022-10-17 | Not applicable | Proof of concept only | The miniOrange Discord Integration WordPress plugin before 2.1.6 does not have authorisation and CSRF in some of its AJAX actions, allowing any logged in users, such as subscriber to call them, and disable the app for example |
| CVE-2022-2987 | High | 2022-09-26 | Not applicable | Proof of concept only | The Ldap WP Login / Active Directory Integration WordPress plugin before 3.0.2 does not have any authorisation and CSRF checks when updating it's settings (which are hooked to the init action), allowing unauthenticated attackers to update them. Attackers could set their own LDAP server to be used to authenticated users, therefore bypassing the current authentication |
| CVE-2020-5398 | High | 2020-01-17 | Mitigation candidate | Proof of concept only | In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a "Content-Disposition" header in the response where the filename attribute is derived from user supplied input. |
| CVE-2018-1270 | Critical | 2018-04-06 | Protected by Waratek | Proof of concept only | Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. |