An issue was discovered in Intesync Solismed 3.3sp1. An flaw in the encryption implementation exists, allowing for all encrypted data stored within the database to be decrypted.
Vendor
intesync vulnerabilities
13 published CVES affecting intesync, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 13
- Critical
- 5
- High
- 3
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest intesync CVEs
Newest publication first
-
MediumCVSS 5.9
-
CriticalCVSS 9.8
Intesync Solismed 3.3sp1 allows Local File Inclusion (LFI), a different vulnerability than CVE-2019-15931. This leads to unauthenticated code execution.
-
CriticalCVSS 9.8
Intesync Solismed 3.3sp allows Insecure File Upload.
-
MediumCVSS 6.1
Intesync Solismed 3.3sp has XSS.
-
HighCVSS 8.8
Intesync Solismed 3.3sp has CSRF.
-
CriticalCVSS 9.8
Intesync Solismed 3.3sp has SQL Injection.
-
CriticalCVSS 9.8
Intesync Solismed 3.3sp has Incorrect Access Control.
-
CriticalCVSS 9.8
Intesync Solismed 3.3sp allows Directory Traversal, a different vulnerability than CVE-2019-16246.
-
MediumCVSS 4.3
Intesync Solismed 3.3sp allows Clickjacking.
-
HighCVSS 7.5 EPSS 0.91%
SQL injection vulnerability in the Survey Pro module for Miniweb 2.0 allows remote attackers to execute arbitrary SQL commands via the campaign_id parameter in a results action to index.php.
-
MediumCVSS 4.3 EPSS 1.2%
Cross-site scripting (XSS) vulnerability in the Survey Pro module for Miniweb 2.0 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO to index.php.
-
HighCVSS 7.5 EPSS 0.91%
SQL injection vulnerability in index.php in the Publisher module 2.0 for Miniweb allows remote attackers to execute arbitrary SQL commands via the historymonth parameter.
-
MediumCVSS 4.3 EPSS 1.2%
Multiple cross-site scripting (XSS) vulnerabilities in index.php in the Publisher module 2.0 for Miniweb allow remote attackers to inject arbitrary web script or HTML via the (1) begin parameter and the (2) PATH_INFO.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.