Sparx Systems Pro Cloud Server up to 6.1 syntactically invalid structure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Sparx Systems Pro Cloud Server up to 6.1. This vulnerability affects unknown code. Performing a manipulation results in improper handling of syntactically invalid structure. This vulnerability was named CVE-2026-42100. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as problematic has been found in Sparx Systems Pro Cloud Server up to 6.1. This affects some unknown functionality. The manipulation with an unknown input leads to a improper handling of syntactically invalid structure vulnerability. CWE is classifying the issue as CWE-228. The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification. This is going to have an impact on availability. The summary by CVE is:
Improper Handling of Syntactically Invalid Structure in Sparx Pro Cloud Server allows Denial of Service (DoS) attack to be executed by sending an specially crafted SQL query. This causes the Pro Cloud Server service to terminate unexpectedly. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.1 (build 167) and below were tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.
The weakness was presented by Blazej Adamczyk. The advisory is shared at cert.pl. This vulnerability is uniquely identified as CVE-2026-42100 since 04/24/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper handling of syntactically invalid structureCWE: CWE-228 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/24/2026 CVE reserved05/19/2026 Advisory disclosed
05/19/2026 VulDB entry created
05/19/2026 VulDB entry last update
Sources
Advisory: cert.plResearcher: Blazej Adamczyk
Status: Not defined
CVE: CVE-2026-42100 (🔒)
GCVE (CVE): GCVE-0-2026-42100
GCVE (VulDB): GCVE-100-364653
Entry
Created: 05/19/2026 15:52Changes: 05/19/2026 15:52 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.