NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
18 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2025-25270 An unauthenticated remote attacker can alter the device configuration in a way to get remote code execution as root with specific configurations. phoenixcontact · charx_sec-3000_firmware, phoenixcontact · charx_sec-3050_firmware, phoenixcontact · charx_sec-3100_firmware +1 2025-07-08 critical9.8 CVE-2024-25995 An unauthenticated remote attacker can modify configurations to perform a remote code execution, gain root rights or perform an DoS due to improper input valid… phoenixcontact · charx_sec-3000_firmware, phoenixcontact · charx_sec-3050_firmware, phoenixcontact · charx_sec-3100_firmware +1 2024-03-12 critical9.8 CVE-2023-46141 Incorrect Permission Assignment for Critical Resource vulnerability in multiple products of the PHOENIX CONTACT classic line allow an remote unauthenticated at… phoenixcontact · automationworx_software_suite, phoenixcontact · axc_1050_firmware, phoenixcontact · axc_1050_xc_firmware +9 2023-12-14 critical9.8 CVE-2023-0757 Incorrect Permission Assignment for Critical Resource vulnerability in PHOENIX CONTACT MULTIPROG, PHOENIX CONTACT ProConOS eCLR (SDK) allows an unauthenticated… phoenixcontact · multiprog, phoenixcontact · proconos_eclr 2023-12-14 critical10.0 CVE-2023-3572 In PHOENIX CONTACTs WP 6xxx series web panels in versions prior to 4.0.10 a remote, unauthenticated attacker may use an attribute of a specific HTTP POST reque… phoenixcontact · wp_6070-wvps_firmware, phoenixcontact · wp_6101-wxps_firmware, phoenixcontact · wp_6121-wxps_firmware +3 2023-08-08 critical9.6 CVE-2023-3526 In PHOENIX CONTACTs TC ROUTER and TC CLOUD CLIENT in versions prior to 2.07.2 as well as CLOUD CLIENT 1101T-TX/TX prior to 2.06.10 an unauthenticated remote at… phoenixcontact · cloud_client_1101t-tx_firmware, phoenixcontact · tc_cloud_client_1002-4g_att_firmware, phoenixcontact · tc_cloud_client_1002-4g_firmware +4 2023-08-08 critical9.8 CVE-2022-31801 An unauthenticated, remote attacker could upload malicious logic to the devices based on ProConOS/ProConOS eCLR in order to gain full control over the device. phoenixcontact · multiprog, phoenixcontact · proconos, phoenixcontact-software · proconos_eclr 2022-06-21 critical9.8 CVE-2022-31800 An unauthenticated, remote attacker could upload malicious logic to devices based on ProConOS/ProConOS eCLR in order to gain full control over the device. phoenixcontact · axc_1050_firmware, phoenixcontact · axc_1050_xc_firmware, phoenixcontact · axc_3050_firmware +9 2022-06-21 critical9.1 CVE-2022-29898 On various RAD-ISM-900-EN-* devices by PHOENIX CONTACT an admin user could use the configuration file uploader in the WebUI to execute arbitrary code with root… phoenixcontact · rad-ism-900-en-bd_firmware, phoenixcontact · rad-ism-900-en-bd\/b_firmware, phoenixcontact · rad-ism-900-en-bd-bus_firmware 2022-05-11 critical9.1 CVE-2022-29897 On various RAD-ISM-900-EN-* devices by PHOENIX CONTACT an admin user could use the traceroute utility integrated in the WebUI to execute arbitrary code with ro… phoenixcontact · rad-ism-900-en-bd_firmware, phoenixcontact · rad-ism-900-en-bd\/b_firmware, phoenixcontact · rad-ism-900-en-bd-bus_firmware 2022-05-11 critical9.4 CVE-2020-8768 An issue was discovered on Phoenix Contact Emalytics Controller ILC 2050 BI before 1.2.3 and BI-L before 1.2.3 devices. phoenixcontact · ilc_2050_bi_firmware, phoenixcontact · ilc_2050_bi-l_firmware 2020-02-17 critical9.8 CVE-2019-9201 Multiple Phoenix Contact devices allow remote attackers to establish TCP sessions to port 1962 and obtain sensitive information or make changes, as demonstrate… phoenixcontact · ilc_131_eth_firmware, phoenixcontact · ilc_131_eth\/xc_firmware, phoenixcontact · ilc_151_eth_firmware +5 2019-02-26 critical9.0 CVE-2018-10731 All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to buffer overflows when handling very large coo… phoenixcontact · fl_switch_3005_firmware, phoenixcontact · fl_switch_3005t_firmware, phoenixcontact · fl_switch_3004t-fx_firmware +9 2018-05-17 critical9.1 CVE-2018-10730 All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to OS command injection. phoenixcontact · fl_switch_3005_firmware, phoenixcontact · fl_switch_3005t_firmware, phoenixcontact · fl_switch_3004t-fx_firmware +9 2018-05-17 critical9.8 CVE-2017-16743 An Improper Authorization issue was discovered in PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, and 48xxx Series products running firmware Version 1.0 to 1.32. phoenixcontact · fl_switch_3005_firmware, phoenixcontact · fl_switch_3005t_firmware, phoenixcontact · fl_switch_3004t-fx_firmware +9 2018-01-12 critical9.0 CVE-2017-10102 Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: RMI). oracle · jdk, oracle · jre, debian · debian_linux +9 2017-08-08 critical9.8 CVE-2017-5159 An issue was discovered on Phoenix Contact mGuard devices that have been updated to Version 8.4.0. phoenixcontact · mguard_firmware 2017-02-13 critical10.0 CVE-2014-9195 Phoenix Contact ProConOs and MultiProg do not require authentication, which allows remote attackers to execute arbitrary commands via protocol-compliant traffi… phoenixcontact-software · multiprog, phoenixcontact-software · proconos_eclr 2015-01-17

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.