Overview 13 matches · 11 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
13matches
11in Waratek scope84.6%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
1public PoC7.7%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
11
84.6%
Outside Waratek scope
0
0.0%
Not applicable
2
15.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
13
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
12
92.3%
Forecast only
0
0.0%
No public exploit
1
7.7%
split by
peak 9 / quarter
Q4 201
Not applicable1
Critical1
not blocked1
Proof of concept only1
Q1 210
Q2 210
Q3 211
No exploit published1
Medium1
not blocked1
No public exploit1
Q4 210
Q1 220
Q2 220
Q3 220
Q4 221
No exploit published1
Medium1
not blocked1
Proof of concept only1
Q1 230
Q2 230
Q3 230
Q4 239
No exploit published9
Medium9
not blocked9
Proof of concept only9
Q1 241
Not applicable1
Medium1
not blocked1
Proof of concept only1
Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-27151 | Medium | 2024-02-29 | Not applicable | Proof of concept only | openCRX 5.2.0 was discovered to contain an HTML injection vulnerability for Search Criteria-Activity Number (in the Saved Search Activity) via the Name, Description, or Activity Number field. |
| CVE-2023-27150 | Medium | 2023-12-26 | No exploit published | Proof of concept only | openCRX 5.2.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the Name field after creation of a Tracker in Manage Activity. |
| CVE-2023-40817 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via the Product Configuration Name Field. |
| CVE-2023-40816 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via Activity Milestone Name Field. |
| CVE-2023-40815 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via the Category Creation Name Field. |
| CVE-2023-40814 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via the Accounts Name Field. |
| CVE-2023-40813 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via Activity Saved Search Creation. |
| CVE-2023-40812 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via the Accounts Group Name Field. |
| CVE-2023-40810 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via Product Name Field. |
| CVE-2023-40809 | Medium | 2023-11-18 | No exploit published | Proof of concept only | OpenCRX version 5.2.0 is vulnerable to HTML injection via the Activity Search Criteria-Activity Number. |
| CVE-2022-40084 | Medium | 2022-10-20 | No exploit published | Proof of concept only | OpenCRX before v5.2.2 was discovered to be vulnerable to password enumeration due to the difference in error messages received during a password reset which could enable an attacker to determine if a username, email or ID is valid. |
| CVE-2021-25959 | Medium | 2021-09-29 | No exploit published | No public exploit | In OpenCRX, versions v4.0.0 through v5.1.0 are vulnerable to reflected Cross-site Scripting (XSS), due to unsanitized parameters in the password reset functionality. This allows execution of external javascript files on any user of the openCRX instance. |
| CVE-2020-7378 | Critical | 2020-11-24 | Not applicable | Proof of concept only | CRIXP OpenCRX version 4.30 and 5.0-20200717 and prior suffers from an unverified password change vulnerability. An attacker who is able to connect to the affected OpenCRX instance can change the password of any user, including admin-Standard, to any chosen value. This issue was resolved in version 5.0-20200904, released September 4, 2020. |