CVE-2019-16246: Intesync Solismed 3.3sp1 allows Local File Inclusion (LFI), a different vulnerability than CVE-2019-15931

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2019-16246 is a critical-severity flaw (CVSS 9.8) affecting solismed. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Intesync Solismed 3.3sp1 allows Local File Inclusion (LFI), a different vulnerability than CVE-2019-15931. This leads to unauthenticated code execution.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.3% (top 11%)
CISA exploited list	No
Weakness	CWE-22
Published	2019-12-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: intesync

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-12-12 14:15 UTCPublished CVE record published
2026-06-17 02:21 UTCUpdated Record last modified

intesync solismed DOWNGRADE

Affected: 3.3 sp1

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.3

1. Check installed version

apt-cache policy solismed || rpm -q solismed || solismed --version

2. No fixed release: DOWNGRADE to a release before 3.3 (Debian / Ubuntu)

apt-cache madison solismed sudo apt install solismed=<VERSION_BEFORE_3.3> sudo apt-mark hold solismed

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list solismed sudo dnf downgrade solismed-<VERSION_BEFORE_3.3> sudo dnf versionlock add solismed

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-16246?

solismed: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-16246 being exploited?

CVE-2019-16246 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-16246 affect?

CVE-2019-16246 affects solismed. Severity is critical (CVSS 9.8). Intesync Solismed 3.3sp1 allows Local File Inclusion (LFI), a different vulnerability than CVE-2019-15931. This leads to unauthenticated code execution.

How urgent is CVE-2019-16246?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-17428 MEDIUM 5.9 DOWNGRADE An issue was discovered in Intesync Solismed 3.3sp1
CVE-2019-15936 CRITICAL 9.8 DOWNGRADE Intesync Solismed 3.3sp allows Insecure File Upload.
CVE-2019-15935 MEDIUM 6.1 DOWNGRADE Intesync Solismed 3.3sp has XSS.
CVE-2019-15934 HIGH 8.8 DOWNGRADE Intesync Solismed 3.3sp has CSRF.
CVE-2019-15933 CRITICAL 9.8 DOWNGRADE Intesync Solismed 3.3sp has SQL Injection.

References

← Back to latest CVEs