R-SeeNet
Advantech
- Product type
- Other
- Catalog vulnerabilities
- 40
Severity across 6 analyzed records
- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Verify to analyze this security profile
As of 09/14/2026, within CyStack's analyzed data, R-SeeNet has 0 security vulnerabilities published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of R-SeeNet and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2023-5642Advantech R-SeeNet Unauthenticated Read/Write | Exploitation statusPublic exploit | FixYes | Published10/18/2023 | SeverityCritical |
CVE-2023-2611Advantech R-SeeNet Use of Hard-coded Credentials | Exploitation statusNot known exploited | FixYes | Published06/22/2023 | SeverityCritical |
CVE-2023-3256Advantech R-SeeNet External Control of File Name or Path | Exploitation statusNot known exploited | FixYes | Published06/22/2023 | SeverityHigh |
CVE-2022-3387 | Exploitation statusNot known exploited | FixYes | Published10/27/2022 | SeverityMedium |
CVE-2022-3386 | Exploitation statusNot known exploited | FixYes | Published10/27/2022 | SeverityCritical |
CVE-2022-3385 | Exploitation statusNot known exploited | FixYes | Published10/27/2022 | SeverityCritical |
CVE-2021-21937 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21936 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21935 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21934 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21933 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21932 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21931 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21930 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21929 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21928 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21927 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21926 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21925 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21924 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21923 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21922 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21921 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21920 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21919 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21918 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21917 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21916 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21915 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21911 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21912 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21910 | Exploitation statusNot confirmed | FixNot confirmed | Published12/22/2021 | SeverityHigh |
CVE-2021-21805 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2021 | SeverityCritical |
CVE-2021-21803 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2021 | SeverityCritical |
CVE-2021-21802 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2021 | SeverityCritical |
CVE-2021-21801 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2021 | SeverityCritical |
CVE-2021-21804 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2021 | SeverityHigh |
CVE-2021-21800 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2021 | SeverityCritical |
CVE-2021-21799 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2021 | SeverityCritical |
CVE-2020-25157 | Exploitation statusNot confirmed | FixNot confirmed | Published10/20/2020 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
