CVE-2025-40819 json
A vulnerability has been identified in SINEMA Remote Connect Server (All versions < V3.2 SP4).
published 2025-12-09 11 mo ago modified 2026-10-23 16 d ago also EUVD-2025-201924
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in SINEMA Remote Connect Server (All versions < V3.2 SP4). Affected applications do not properly validate license restrictions against the database, allowing direct modification of the system_ticketinfo table to bypass license limitations without proper enforcement checks. This could allow with database access to circumvent licensing restrictions by directly modifying database values and potentially enabling unauthorized use beyond the permitted scope.
Patch / fix
- Siemens SINEMA Remote Connect Server V3.2 SP4
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-25-345-06 updated cvss 4.3
Siemens SINEMA Remote Connect Server
-
Siemens SINEMA Remote Connect Server <V3.2_SP4affected: fixed in V3.2 support.industry.siemens.com
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- Siemens SINEMA Remote Connect Server
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
cert-portal.siemens.com
/productcert/html/ssa-626856.html
vendor-advisory
Sources
- CVE List CVE-2025-40819
- NVD CVE-2025-40819
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.