A vulnerability has been identified in SPPA-T3000 Application Server (All versions < Service Pack R8.2 SP2).

published 2019-12-12 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-8077

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 4.0%; EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits: 0; none known

A vulnerability has been identified in SPPA-T3000 Application Server (All versions < Service Pack R8.2 SP2). An attacker with valid authentication at the RMI interface could be able to gain remote code execution through an unsecured file upload. Please note that an attacker needs to have access to the Application Highway in order to exploit this vulnerability. At the time of advisory publication no public exploitation of this security vulnerability was known.

Patch / fix

fixed in 1

siemens sppa-t3000_application_server r8.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-19-351-02 updated 2025-05-06 cvss 8.8

Siemens SPPA-T3000 (Update A)

Siemens SPPA-T3000 Application Server <Service_Pack_R8.2_SP2
affected: vendor fix, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

4.01% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

Siemens SPPA-T3000 Application Server

Classification

Weakness

CWE-434 Unrestricted Upload of File with Dangerous Type
CWE-787 Out-of-bounds Write

References

cert-portal.siemens.com /productcert/pdf/ssa-451445.pdf
mitigation, vendor-advisory
packetstormsecurity.com /files/155665/Siemens-Security-Advisory-SPPA-T3000-Code-Execution.html
third-party-advisory, vdb-entry

Sources

CVE List CVE-2019-18288
NVD CVE-2019-18288

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary