Skip to content
Fencer Intel
critical 9.1

CVE-2025-3200 json

Com-Server Exposed via Weak TLS

published last yr. modified 4mo ago also EUVD-2025-12562

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

An unauthenticated remote attacker could exploit the used, insecure TLS 1.0 and TLS 1.1 protocols to intercept and manipulate encrypted communications between the Com-Server and connected systems.

Patch / fix

  • Wiesemann & Theis Com-Server++ 1.60
  • Wiesemann & Theis Com-Server PoE 3x Isolated 1.60
  • Wiesemann & Theis Com-Server 20mA 1.60
  • Wiesemann & Theis Com-Server OEM 1.60
  • Wiesemann & Theis Com-Server UL 1.60

Is CVE-2025-3200 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Wiesemann & Theis Com-Server++
  • Wiesemann & Theis Com-Server PoE 3x Isolated
  • Wiesemann & Theis Com-Server 20mA
  • Wiesemann & Theis Com-Server OEM
  • Wiesemann & Theis Com-Server UL

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel 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.