NetSight

Security Dashboard

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

Reset
43 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2025-34093 An authenticated command injection vulnerability exists in the Polycom HDX Series command shell interface accessible over Telnet. 2025-07-10 high7.5 CVE-2025-22918 Polycom RealPresence Group 500 <=20 has Insecure Permissions due to automatically loaded cookies. 2025-02-03 high8.8 CVE-2023-29930 An issue was found in Genesys CIC Polycom phone provisioning TFTP Server all version allows a remote attacker to execute arbitrary code via the login crednetia… genesys · tftp_server 2023-05-10 high8.8 CVE-2021-41322 Poly VVX 400/410 5.3.1 allows low-privileged users to change the Admin password by modifying a POST parameter to 120 during the password reset process. polycom · vvx_400_firmware, polycom · vvx_410_firmware 2021-10-04 high7.2 CVE-2021-37145 A command-injection vulnerability in an authenticated Telnet connection in Poly (formerly Polycom) CX5500 and CX5100 1.3.5 leads an attacker to Privilege Escal… poly · cx5500_firmware, poly · cx5100_firmware 2021-09-07 high7.2 CVE-2019-11355 An issue was discovered in Poly (formerly Polycom) HDX 3.1.13. polycom · hdx_system_software 2020-03-12 critical9.8 CVE-2012-6611 An issue was discovered in Polycom Web Management Interface G3/HDX 8000 HD with Durango 2.6.0 4740 software and embedded Polycom Linux Development Platform 2.1… polycom · hdx_system_software 2020-02-10 high8.8 CVE-2012-6610 Polycom HDX Video End Points before 3.0.4 and UC APL before 2.7.1.J allows remote authenticated users to execute arbitrary commands as demonstrated by a ; (sem… polycom · hdx_video_end_points, polycom · uc_apl 2020-01-28 high7.5 CVE-2012-6609 Directory traversal vulnerability in a_getlog.cgi in Polycom HDX Video End Points before 3.0.4 and UC APL before 2.7.1.J allows remote attackers to read arbitr… polycom · hdx_video_end_points, polycom · uc_apl 2020-01-28 high8.0 CVE-2019-14259 On the Polycom Obihai Obi1022 VoIP phone with firmware 5.1.11, a command injection (missing input validation) issue in the NTP server IP address field for the … polycom · obihai_obi1022_firmware 2019-08-01 high8.3 CVE-2019-12948 A vulnerability in the web-based management interface of VVX, Trio, SoundStructure, SoundPoint, and SoundStation phones running Polycom UC Software, if exploit… polycom · unified_communications_software, polycom · united_communications_software 2019-07-29 medium6.5 CVE-2019-10689 VVX products using UCS software version 5.9.2 and earlier with Better Together over Ethernet Connector (BToE) application version 3.9.1 and earlier provides in… polycom · better_together_over_ethernet_connector, polycom · unified_communications_software 2019-06-24 low3.1 CVE-2018-10947 An issue was discovered in versions earlier than 1.3.2 for Polycom RealPresence Debut where the admin cookie is reset only after a Debut is rebooted. polycom · realpresence_debut_firmware 2019-06-13 medium6.8 CVE-2018-10946 An issue was discovered in versions earlier than 1.3.0-66872 for Polycom RealPresence Debut that allows attackers to arbitrarily read the admin user's password… polycom · realpresence_debut_firmware 2019-06-13 critical9.8 CVE-2018-15128 An issue was discovered in Polycom Group Series 6.1.6.1 and earlier, HDX 3.1.12 and earlier, and Pano 1.1.1 and earlier. polycom · group_series, polycom · hdx, polycom · pano 2019-05-13 medium6.8 CVE-2019-10688 VVX products with software versions including and prior to, UCS 5.9.2 with Better Together over Ethernet Connector (BToE) application 3.9.1, use hard-coded cre… polycom · unified_communications_software, polycom · better_together_over_ethernet_connector 2019-04-23 medium6.1 CVE-2018-14935 The Web administration console on Polycom Trio devices with software before 5.5.4 has XSS. polycom · trio_8500_firmware 2018-11-15 medium6.5 CVE-2018-14934 The Bluetooth subsystem on Polycom Trio devices with software before 5.5.4 has Incorrect Access Control. polycom · trio_8500_firmware 2018-11-15 medium5.9 CVE-2018-18568 Polycom VVX 500 and 601 devices 5.8.0.12848 and earlier allows man-in-the-middle attackers to obtain sensitive credential information by leveraging failure to … polycom · unified_communications_software, polycom · vvx_601_firmware, polycom · vvx_500_firmware 2018-10-24 medium5.3 CVE-2018-18566 The SIP service in Polycom VVX 500 and 601 devices 5.8.0.12848 and earlier allow remote attackers to obtain sensitive phone configuration information by levera… polycom · unified_communications_software, polycom · vvx_601_firmware, polycom · vvx_500_firmware 2018-10-24 high7.5 CVE-2018-12592 Polycom RealPresence Web Suite before 2.2.0 does not block a user's video for a few seconds upon joining a meeting (when the user has explicitly chosen to turn… polycom · realpresence_web_suite 2018-06-20 high8.8 CVE-2018-7565 CSRF exists on Polycom QDX 6000 devices. polycom · qdx_6000_firmware 2018-03-07 medium6.1 CVE-2018-7564 Stored XSS exists on Polycom QDX 6000 devices. polycom · qdx_6000_firmware 2018-03-07 high7.0 CVE-2015-4685 Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allows local users with access to the plcm account to gain privileges via a script in /var/polycom/… polycom · realpresence_resource_manager 2017-09-19 medium6.5 CVE-2015-4684 Multiple directory traversal vulnerabilities in Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allow (1) remote authenticated users to read arbitr… polycom · realpresence_resource_manager 2017-09-19 critical9.8 CVE-2015-4683 Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allows attackers to obtain sensitive information and potentially gain privileges by leveraging use … polycom · realpresence_resource_manager 2017-09-19 medium6.5 CVE-2015-4682 Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allows remote authenticated users to obtain the installation path via an HTTP POST request to PlcmR… polycom · realpresence_resource_manager 2017-09-19 high7.8 CVE-2015-4681 Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allows local users to have unspecified impact via vectors related to weak passwords. polycom · realpresence_resource_manager 2017-09-19 high7.8 CVE-2015-8300 Polycom BToE Connector before 3.0.0 uses weak permissions (Everyone: Full Control) for "Program Files (x86)\polycom\polycom btoe connector\plcmbtoesrv.exe," wh… polycom · btoe_connector 2017-08-28 high8.8 CVE-2017-12857 Polycom SoundStation IP, VVX, and RealPresence Trio that are running software older than UCS 4.0.12, 5.4.5 rev AG, 5.4.7, 5.5.2, or 5.6.0 are affected by a vul… polycom · unified_communications_software 2017-08-25

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.