How severe is CVE-2026-42097?

CVE-2026-42097 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-42097 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (57th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-42097?

CVE-2026-42097 affects Sparxsystems Pro Cloud Server. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-42097?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-42097 have an EU (EUVD) identifier?

Yes. CVE-2026-42097 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-30931.

When was CVE-2026-42097 published?

CVE-2026-42097 was published on 2026-05-19 and last updated on 2026-06-17.

CVE-2026-42097

CVE-2026-42097 is a high-severity vulnerability in Sparxsystems Pro Cloud Server with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v4: 9.3
EPSS exploit prediction: 1% (57th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-30931
Weakness: CWE-639
Affected product: Sparxsystems Pro Cloud Server
Published: 2026-05-19
Last modified: 2026-06-17

Description

Sparx Pro Cloud Server requires authentication based on requested URL. An attacker can omit the "model" query parameter and send the model name only in the binary blob in POST request allowing SQL query execution without authentication. 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.

Frequently asked questions

What is CVE-2026-42097?: Sparx Pro Cloud Server requires authentication based on requested URL. An attacker can omit the "model" query parameter and send the model name only in the binary blob in POST request allowing SQL query execution without authentication. 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.
How severe is CVE-2026-42097?: CVE-2026-42097 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-42097 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (57th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-42097?: CVE-2026-42097 affects Sparxsystems Pro Cloud Server. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-42097?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-42097 have an EU (EUVD) identifier?: Yes. CVE-2026-42097 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-30931.
When was CVE-2026-42097 published?: CVE-2026-42097 was published on 2026-05-19 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:sparxsystems:pro_cloud_server:*:*:*:*:*:*:*:*

More vulnerabilities in Sparxsystems Pro Cloud Server

CVE-2025-15625 — Critical (CVSS 9.8): Unauthenticated user is able to execute arbitrary SQL commands in Sparx Pro Cloud Server database in certain cases.
CVE-2026-42096 — High (CVSS 8.8): Sparx Pro Cloud Server is vulnerable to Broken Access Control within communication with the database. Due to lack of…
CVE-2026-42100 — High (CVSS 7.5): Improper Handling of Syntactically Invalid Structure in Sparx Pro Cloud Server allows Denial of Service (DoS) attack to…
CVE-2026-42099 — High (CVSS 7.5): Sparx Pro Cloud Server is vulnerable to a Race Condition in the /data_api/dl_internal_artifact.php endpoint. The…
CVE-2025-15624 — High (CVSS 7.5): Plaintext Storage of a Password vulnerability in Sparx Systems Pty Ltd. Sparx Pro Cloud Server. In a setup where…
CVE-2025-15623 — High (CVSS 7.5): Exposure of Private Personal Information to an Unauthorized Actor, : Exposure of Sensitive System Information to an…

All CVEs affecting Sparxsystems Pro Cloud Server →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

CVE-2025-40805 — Critical (CVSS 10.0): Affected devices do not properly enforce user authentication on specific API endpoints. This could facilitate an…
CVE-2024-45032 — Critical (CVSS 10.0): A vulnerability has been identified in Industrial Edge Management Pro (All versions < V1.9.5), Industrial Edge…
CVE-2026-34037 — Critical (CVSS 9.9): Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to…
CVE-2026-52782 — Critical (CVSS 9.9): OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, there is an IDOR through…
CVE-2026-45552 — Critical (CVSS 9.9): Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. In versions 8.2.6.4 and prior,…
CVE-2026-29200 — Critical (CVSS 9.9): A critical IDOR vulnerability has been discovered in Comet Backup affecting all versions from 20.11.0 to 26.1.1 and…

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →