CVE-2025-15132VulnerabilityPublished 28 Dec 2025Updated 29 Dec 2025

CVE-2025-15132: ZSPACE Z4Pro+ · Command Injection

Affects ZSPACE Z4Pro+Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 7.6% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubzspace/Z4Pro+`pkg:github/zspace/Z4Pro+`Other threats	Affected =1.0.0440024	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor vendor communications closely for official patches or firmware updates addressing CVE-2025-15132 and apply them promptly once available. 2. Implement network segmentation to isolate ZSPACE Z4Pro+ devices from critical infrastructure and limit exposure to untrusted networks. 3. Employ web application firewalls (WAFs) or intrusion prevention systems (IPS) to detect and block malicious HTTP POST requests targeting the /v2/file/safe/open endpoint. 4. Restrict access to the affected API endpoint using network access controls, VPNs, or authentication gateways to reduce attack surface. 5. Conduct regular vulnerability scans and penetration tests focusing on ZSPACE devices to identify potential exploitation attempts. 6. Enforce strict input validation and sanitization policies on any custom integrations or middleware interacting with ZSPACE APIs. 7. Maintain comprehensive logging and monitoring to detect anomalous command execution or suspicious activities on Z4Pro+ devices. 8. Educate IT and security teams about this vulnerability and ensure incident response plans include scenarios involving ZSPACE device compromise. 9. If immediate patching is not feasible, consider temporarily disabling or restricting access to the vulnerable API endpoint to mitigate risk. 10. Collaborate with ZSPACE support for guidance and best practices tailored to your deployment environment.

Description

A vulnerability was determined in ZSPACE Z4Pro+ 1.0.0440024. The affected element is the function zfilev2_api_open of the file /v2/file/safe/open of the component HTTP POST Request Handler. This manipulation causes command injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure.

Impact

For European organizations, the impact of CVE-2025-15132 depends on the deployment scale of ZSPACE Z4Pro+ devices. Organizations using these devices in critical workflows such as design, training, or research could face operational disruptions if attackers exploit the vulnerability to execute arbitrary commands. Confidential information processed or stored on these devices could be exposed or altered, affecting data integrity and privacy compliance under regulations like GDPR. The availability of affected systems could be compromised, leading to downtime and productivity loss. Since the vulnerability allows remote exploitation without user interaction, attackers could target exposed devices over the internet or internal networks. The medium severity rating suggests that while the threat is significant, it may not lead to full system compromise without additional vulnerabilities or misconfigurations. However, the public disclosure of exploit code increases the likelihood of attacks, necessitating proactive defense measures. European sectors such as manufacturing, education, and research institutions that adopt ZSPACE technology are particularly at risk. The potential reputational damage and regulatory consequences from data breaches further elevate the impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Dec 2025, 23:19 UTC

Technical details

References

Community reviews

Related threats