Overview 6 matches · 1 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 3 public PoC · 0 EPSS ≥ 0.5
6matches
1in Waratek scope16.7%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
3public PoC50.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
1
16.7%
Outside Waratek scope
0
0.0%
Not applicable
5
83.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
6
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
3
50.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
3
50.0%
split by
peak 2 / year
20041
Not applicable1
Medium1
not blocked1
Working exploit published1
20051
Not applicable1
Medium1
not blocked1
Working exploit published1
20060
20070
20080
20090
20101
Not applicable1
Medium1
not blocked1
Working exploit published1
20110
20120
20130
20140
20150
20160
20170
20180
20190
20202
Not applicable2
Medium2
not blocked2
No public exploit2
20210
20220
20230
20240
20250
20261
No exploit published1
Medium1
not blocked1
No public exploit1
200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-34164 | Medium | 2026-04-16 | No exploit published | No public exploit | Valtimo is an open-source business process automation platform. In versions 13.0.0 through 13.21.0, the InboxHandlingService logs the full content of every incoming inbox message at INFO level. Inbox messages can contain highly sensitive information including personal data (PII), citizen identifiers (BSN), and case details. This data is exposed to anyone with access to application logs or any Valtimo user with the admin role through the Admin UI logging module. This issue has been fixed in version 13.22.0. If developers are unable to upgrade immediately, they can restrict access to application logs and adjust the log level for com.ritense.inbox to WARN or higher in their application configuration as a workaround. |
| CVE-2020-5721 | Medium | 2020-04-15 | Not applicable | No public exploit | MikroTik WinBox 3.22 and below stores the user's cleartext password in the settings.cfg.viw configuration file when the Keep Password field is set and no Master Password is set. Keep Password is set by default and, by default Master Password is not set. An attacker with access to the configuration file can extract a username and password to gain access to the router. |
| CVE-2020-5720 | Medium | 2020-02-06 | Not applicable | No public exploit | MikroTik WinBox before 3.21 is vulnerable to a path traversal vulnerability that allows creation of arbitrary files wherevere WinBox has write permissions. WinBox is vulnerable to this attack if it connects to a malicious endpoint or if an attacker mounts a man in the middle attack. |
| CVE-2010-1353 | Medium | 2010-04-12 | Not applicable | Working exploit published | Directory traversal vulnerability in the LoginBox Pro (com_loginbox) component for Joomla! allows remote attackers to read arbitrary files via a .. (dot dot) in the view parameter to index.php. |
| CVE-2005-1606 | Medium | 2005-05-16 | Not applicable | Working exploit published | H-Sphere Winbox 2.4.2 and 2.4.3 RC1 stores sensitive information such as username and password in plaintext in world-readable log files, which allows local users to gain privileges. |
| CVE-2004-1878 | Medium | 2004-03-30 | Not applicable | Working exploit published | LINBOX LIN:BOX allows remote attackers to bypass authentication, obtain sensitive information, or gain access via a direct request to admin/user.pl preceded by // (double leading slash). |