Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Pro Cloud Server repository
-
DeliveryCraft dl_internal_artifact.php request with malicious guid
-
ExploitStage PHP webshell with large/slow payload
-
ExecutionRace second HTTP request before cleanup
-
PersistExecute webshell as web server user
-
ImpactEstablish foothold on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires authenticated access to the Sparx Pro Cloud Server repository (CVSS PR:L) sufficient to invoke /data_api/dl_internal_artifact.php and supply a guid pointing to an attacker-controlled object whose properties include both filename and contents. The attacker must also be able to influence transmission timing - typically by uploading or referencing a large artifact, or by throttling their own TCP receive window - to keep the staged .php file on disk long enough for a parallel request to fetch it (CVSS AC:H attack complexity and AT:P attack requirement reflect this race window). Limiting factors: requires a valid repository account (not anonymous), requires the deployment to expose the dl_internal_artifact.php endpoint to the attacker's network path, requires the PHP interpreter to execute files in the directory where artifacts are temporarily written, and success is probabilistic per attempt because the window closes when cleanup completes. |
| Impact | CVSS 4.0 scores this 7.7 (High) with vector AV:N/AC:H/AT:P/PR:L/UI:N - network reachable but with high attack complexity, a present attack requirement (the race window), and low privileges (an authenticated repository user). Confidentiality, integrity, and availability impact on the vulnerable system are all High, with low subsequent-system impact. No EPSS score, KEV listing, or SSVC decision data was supplied, and no public exploit identified at time of analysis, though three independent technical write-ups (CERT-PL, sploit.tech, efigo.pl) describe the bug in detail, which materially lowers the cost of weaponization. Realistic priority is moderate-to-high for any organization exposing Pro Cloud Server to untrusted or semi-trusted repository users; it is lower for hardened, internal-only deployments where repository accounts are tightly controlled. Key missing data: vendor never confirmed the full vulnerable version range, so versions above 6.1 build 167 are of unknown status - a meaningful gap for patch planning. |
| Exploit ScenarioDerived | An attacker with a valid low-privilege repository account on a publicly reachable Pro Cloud Server crafts a request to /data_api/dl_internal_artifact.php with a guid pointing to an object whose name is a .php file and whose contents are a PHP webshell. They artificially slow the download (large payload or throttled TCP receive window) to widen the post-write, pre-delete race window, then issue a parallel HTTP request to fetch the staged .php file, triggering execution as the web server user. Detailed write-ups exist on cert.pl, sploit.tech, and efigo.pl, lowering the engineering effort to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 19, 2026
Remote code execution in Sparx Systems Pro Cloud Server (versions 0 through 6.1 build 167) is achievable by authenticated repository users via a race condition in the /data_api/dl_internal_artifact.php endpoint. An attacker who controls both the filename and contents of a downloaded artifact can briefly stage a malicious PHP file in the web root and execute it before cleanup, leading to full server compromise. No public exploit identified at time of analysis, but a detailed technical write-up published by CERT-PL and sploit.tech reduces the barrier to reproduction.
RemediationAI
No vendor-released patch identified at time of analysis - Sparx Systems did not respond to coordinated disclosure by CERT-PL, so administrators should contact the vendor directly for a fixed build and monitor https://sparxsystems.com/products/procloudserver/ for updates. As compensating controls, restrict network access to /data_api/dl_internal_artifact.php at a reverse proxy or WAF layer so that only trusted client IPs can reach it (side effect: may break legitimate remote Enterprise Architect clients that need the artifact API); tighten repository account provisioning and audit who currently holds repository access, since exploitation requires PR:L; and where feasible, configure the PHP runtime or web server to deny execution of .php files written to artifact-handling directories (side effect: may break legitimate features that rely on dynamic PHP in those paths). Refer to the technical advisories at https://cert.pl/en/posts/2026/05/CVE-2026-42096, https://sploit.tech/2026/05/19/Sparx-Enterprise-Architect-PCS.html, and https://efigo.pl/blog/CVE-2026-42096/ for detection guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in a PHP-based artifact download handler in Sparx Pro Cloud Server, a collaborative repository backend for Sparx Enterprise Architect modeling tools (CPE: cpe:2.3:a:sparx_systems:pro_cloud_server). The endpoint dl_internal_artifact.php fetches an object identified by the guid parameter and writes its contents to __DIR__ (the current script directory inside the web-accessible PHP application) using an attacker-controlled filename. The root cause is CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization, aka TOCTOU): the write-then-delete sequence is not atomic with respect to concurrent HTTP requests, leaving a window where the file is present and executable by the PHP interpreter. Because the file lands inside a PHP-served directory rather than an isolated quarantine path, any window of exposure becomes code-execution-capable.
Know when Pro Cloud Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
Primary rating from Vendor (CERT-PL) · only source for this CVE.
CVSS VectorVendor: CERT-PL
DescriptionCVE.org
Sparx Pro Cloud Server is vulnerable to a Race Condition in the /data_api/dl_internal_artifact.php endpoint. The application downloads the properties of the object pointed by guid parameter and saves loaded content in current location (__DIR__) under the specified name. An attacker with repository access can control both the filename and file contents, allowing the creation of a malicious PHP file in a current directory. Although the file is deleted after processing, a race condition exists: if the response transmission is delayed (e.g., via a large file or slow client connection), the file remains accessible. During this window, the attacker can issue a second request to execute the malicious PHP file, resulting in remote code execution.
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.
Executive ViewAI
Sparx Systems Pro Cloud Server versions 0 through 6.1 build 167 contain a race condition allowing authenticated users to execute arbitrary code and compromise the entire server. Organizations relying on this platform face complete infrastructure takeover and data breach risk if accessed by malicious insiders or through compromised legitimate credentials.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict network access to the server via firewall rules limiting connections to verified trusted IP addresses; (2) Reduce authenticated user accounts to essential personnel only and implement MFA on all repository access; (3) Deploy real-time alerting on the vulnerable /data_api/dl_internal_artifact.php endpoint to detect rapid download attempts or unusual artifact access patterns; (4) Implement network segmentation to contain potential compromise; (5) Enable comprehensive audit logging to support forensic investigation if compromise is detected.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Pro Cloud Server
View allUnauthenticated SQL execution affects Sparx Pro Cloud Server when attackers omit the 'model' query parameter from the UR
Broken access control in Sparx Systems Pro Cloud Server 6.1 (build 167) and earlier allows authenticated low-privileged
Denial of service in Sparx Systems Pro Cloud Server 6.1 (build 167) and earlier allows authenticated remote attackers to
EUVD-2026-30929
GHSA-qff4-m3j5-xcv5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB