NetSight

Security Dashboard

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

Reset
45 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.4 CVE-2026-5804 An improper authentication vulnerability was discovered in the Motorola Factory Test component (com.motorola.motocit). 2026-05-19 high7.8 CVE-2020-36982 Motorola Device Manager 2.5.4 contains an unquoted service path vulnerability in the MotoHelperService.exe service that allows local users to potentially injec… 2026-01-27 high7.8 CVE-2020-36981 Motorola Device Manager 2.4.5 contains an unquoted service path vulnerability in the PST Service that allows local users to potentially execute arbitrary code. 2026-01-27 high7.0 CVE-2025-1700 A DLL hijacking vulnerability was reported in the Motorola Software Fix (Rescue and Smart Assistant) installer that could allow a local attacker to escalate pr… 2025-07-17 high8.0 CVE-2024-45880 A command injection vulnerability exists in Motorola CX2L router v1.0.2 and below. 2024-10-08 high7.2 CVE-2022-4002 A command injection vulnerability could allow an authenticated user to execute operating system commands as root via a specially crafted API request. motorola · q14_firmware 2024-07-31 high8.1 CVE-2022-27813 Motorola MTM5000 series firmwares lack properly configured memory protection of pages shared between the OMAP-L138 ARM and DSP cores. motorola · mtm5500_firmware, motorola · mtm5400_firmware 2023-10-19 high8.8 CVE-2022-26943 The Motorola MTM5000 series firmwares generate TETRA authentication challenges using a PRNG using a tick count register as its sole entropy source. motorola · mtm5500_firmware, motorola · mtm5400_firmware 2023-10-19 high8.2 CVE-2022-26942 The Motorola MTM5000 series firmwares lack pointer validation on arguments passed to trusted execution environment (TEE) modules. motorola · mtm5500_firmware, motorola · mtm5400_firmware 2023-10-19 high8.4 CVE-2023-23774 Motorola EBTS/MBTS Site Controller drops to debug prompt on unhandled exception. motorola · ebts_site_controller_firmware, motorola · mbts_site_controller_firmware 2023-08-29 high7.2 CVE-2023-23773 Motorola EBTS/MBTS Base Radio fails to check firmware authenticity. motorola · ebts_base_radio_firmware, motorola · mbts_base_radio_firmware 2023-08-29 high7.2 CVE-2023-23772 Motorola MBTS Site Controller fails to check firmware update authenticity. motorola · mbts_site_controller_firmware 2023-08-29 high8.4 CVE-2023-23771 Motorola MBTS Base Radio accepts hard-coded backdoor password. motorola · mbts_base_radio_firmware 2023-08-29 high8.8 CVE-2023-31531 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the tomography_ping_number parameter. motorola · cx2l_firmware 2023-05-11 high8.8 CVE-2023-31530 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the smartqos_priority_devices parameter. motorola · cx2l_firmware 2023-05-11 high8.8 CVE-2023-31529 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the system_time_timezone parameter. motorola · cx2l_firmware 2023-05-11 high8.8 CVE-2023-31528 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the staticroute_list parameter. motorola · cx2l_firmware 2023-05-11 high7.2 CVE-2022-34885 An improper input sanitization vulnerability in the Motorola MR2600 router could allow a local user with elevated permissions to execute arbitrary code. motorola · mr2600_firmware 2023-01-30 high7.5 CVE-2022-30276 The Motorola MOSCAD and ACE line of RTUs through 2022-05-02 omit an authentication requirement. motorola · moscad_ip_gateway_firmware, motorola · ace_ip_gateway_\(4600\)_firmware 2022-07-26 high7.2 CVE-2022-30272 The Motorola ACE1000 RTU through 2022-05-02 mishandles firmware integrity. motorola · ace1000_firmware 2022-07-26 high8.8 CVE-2022-30269 Motorola ACE1000 RTUs through 2022-05-02 mishandle application integrity. motorola · ace1000_firmware 2022-07-26 high7.5 CVE-2022-30275 The Motorola MOSCAD Toolbox software through 2022-05-02 relies on a cleartext password. motorolasolutions · mdlc 2022-07-26 high8.8 CVE-2021-3577 An unauthenticated remote code execution vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an attacker on the same n… binatoneglobal · halo\+_camera_firmware, binatoneglobal · comfort_85_connect_firmware, binatoneglobal · mbp3855_firmware +9 2021-11-12 high7.5 CVE-2020-21934 An issue was discovered in Motorola CX2 router CX 1.0.2 Build 20190508 Rel.97360n where authentication to download the Syslog could be bypassed. motorola · cx2_firmware 2021-07-21 high7.5 CVE-2020-21933 An issue was discovered in Motorola CX2 router CX 1.0.2 Build 20190508 Rel.97360n where the admin password and private key could be found in the log tar packag… motorola · cx2_firmware 2021-07-21 high8.1 CVE-2021-3460 The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could… motorola · mh702x_firmware 2021-04-13 high7.5 CVE-2020-10875 Motorola FX9500 devices allow remote attackers to conduct absolute path traversal attacks, as demonstrated by PL/SQL Server Pages files such as /include/viewta… zebra · fx9500_firmware 2020-03-23 high7.5 CVE-2020-10874 Motorola FX9500 devices allow remote attackers to read database files. motorola · fx9500-41324d41-us_firmware, motorola · fx9500-41324d41-ww_firmware, motorola · fx9500-81324d41-us_firmware +1 2020-03-23 high7.5 CVE-2019-15513 An issue was discovered in OpenWrt libuci (aka Library for the Unified Configuration Interface) before 15.05.1 as used on Motorola CX2L MWR04L 1.01 and C1 MWR0… openwrt · libuci, motorola · cx2l_mwr04l_firmware, motorola · c1_mwr03_firmware 2019-08-23 high7.5 CVE-2019-13129 On the Motorola router CX2L MWR04L 1.01, there is a stack consumption (infinite recursion) issue in scopd via TCP port 8010 and UDP port 8080. motorola · cx2l_mwr04l_firmware 2019-07-01

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.