Intesync Solismed 3.3sp has Incorrect Access Control.

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

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

Is CVE-2019-15932 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

Exploit prediction

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

Exploits and checks

know.bishopfox.com https://know.bishopfox.com/advisories/solismed-critical referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality
CWE-862 Missing Authorization

References

know.bishopfox.com /advisories/solismed-critical
exploit, third-party-advisory
bishopfox.com /blog/news-category/advisories/
third-party-advisory
solismed.com /
product
bishopfox.com
third-party-advisory

Sources

CVE List CVE-2019-15932
NVD CVE-2019-15932

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.