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 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-36438 An issue in Intelbras VIP-1230-D-G4 Version V2.800.00IB00C.0.T allows a remote attacker to obtain sensitive information via password reset functionality under … 2026-05-18 medium6.3 CVE-2026-3101 A vulnerability was found in Intelbras TIP 635G 1.12.3.5. intelbras · tip_635g_firmware 2026-02-24 medium5.3 CVE-2025-13221 A weakness has been identified in Intelbras UnniTI 24.07.11. 2025-11-15 medium5.3 CVE-2025-13187 A security vulnerability has been detected in Intelbras ICIP 2.0.20. intelbras · icip_30_firmware 2025-11-14 medium6.5 CVE-2025-50405 Intelbras RX1500 Router v2.2.17 and before is vulnerable to Incorrect Access Control in the FirmwareUpload function and GetFirmwareValidation function. intelbras · rx_1500_firmware 2025-07-01 medium5.3 CVE-2025-50404 Intelbras RX1500 Router v2.2.17 and before is vulnerable to Integer Overflow. intelbras · rx_1500_firmware 2025-07-01 medium6.3 CVE-2025-6765 A vulnerability, which was classified as critical, has been found in Intelbras InControl 2.21.60.9. intelbras · incontrol_web 2025-06-27 medium4.3 CVE-2024-12897 A vulnerability was found in Intelbras VIP S3020 G2, VIP S4020 G2, VIP S4020 G3 and VIP S4320 G2 up to 20241222. 2024-12-23 medium5.3 CVE-2024-12896 A vulnerability was found in Intelbras VIP S3020 G2, VIP S4020 G2, VIP S4020 G3 and VIP S4320 G2 up to 20241222 and classified as problematic. 2024-12-22 medium6.3 CVE-2024-9324 A vulnerability was found in Intelbras InControl up to 2.21.57. intelbras · incontrol_web 2024-09-29 medium5.3 CVE-2024-3160 ** DISPUTED ** A vulnerability, which was classified as problematic, was found in Intelbras MHDX 1004, MHDX 1008, MHDX 1016, MHDX 5016, HDCVI 1008 and HDCVI 10… 2024-04-02 medium5.4 CVE-2022-24654 Authenticated stored cross-site scripting (XSS) vulnerability in "Field Server Address" field in INTELBRAS ATA 200 Firmware 74.19.10.21 allows attackers to inj… intelbras · ata_200_firmware 2022-08-15 medium5.4 CVE-2020-12262 Intelbras TIP200 60.61.75.15, TIP200LITE 60.61.75.15, and TIP300 65.61.75.15 devices allow /cgi-bin/cgiServer.exx?page= XSS. intelbras · tip200_firmware, intelbras · tip200lite_firmware, intelbras · tip300_firmware 2020-11-27 medium5.3 CVE-2020-13886 Intelbras TIP 200 60.61.75.15, TIP 200 LITE 60.61.75.15, and TIP 300 65.61.75.22 devices allow cgi-bin/cgiServer.exx?page=../ Directory Traversal. intelbras · tip200_firmware, intelbras · tip200lite_firmware, intelbras · tip300_firmware 2020-11-26 medium6.5 CVE-2019-19516 Intelbras WRN 150 1.0.18 devices allow CSRF via GO=system_password.asp to the goform/SysToolChangePwd URI to change a password. intelbras · wrn_150_firmware 2019-12-02 medium6.1 CVE-2019-17222 An issue was discovered on Intelbras WRN 150 1.0.17 devices. intelbras · wrn_150_firmware 2019-11-07 medium6.1 CVE-2018-17337 Intelbras NPLUG 1.0.0.14 devices have XSS via a crafted SSID that is received via a network broadcast. intelbras · nplug_firmware 2018-10-10 medium6.1 CVE-2017-14219 XSS (persistent) on the Intelbras Wireless N 150Mbps router with firmware WRN 240 allows attackers to steal wireless credentials without being connected to the… intelbras · wrn_240_firmware 2017-09-07

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.