NetSight

Security Dashboard

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

Reset
22 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.9 CVE-2025-65081 An out-of-bounds read vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2026-02-03 medium6.9 CVE-2025-65080 A type confusion vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2026-02-03 medium6.9 CVE-2025-65079 A heap-based buffer overflow vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2026-02-03 medium6.9 CVE-2025-9269 A Server-Side Request Forgery (SSRF) vulnerability has been identified in the embedded web server in various Lexmark devices. 2025-09-09 medium6.1 CVE-2020-13481 Certain Lexmark products through 2020-05-25 allow XSS which allows an attacker to obtain session credentials and other sensitive information. 2025-02-19 medium4.3 CVE-2023-50738 A new feature to prevent Firmware downgrades was recently added to some Lexmark products. 2025-01-17 medium5.4 CVE-2020-10094 A cross-site scripting (XSS) vulnerability in Lexmark CS31x before LW74.VYL.P273; CS41x before LW74.VY2.P273; CS51x before LW74.VY4.P273; CX310 before LW74.GM2… lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cs51x_firmware +9 2020-04-28 medium5.4 CVE-2020-10093 A cross-site scripting (XSS) vulnerability in Lexmark Pro910 series inkjet and other discontinued products. lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cs51x_firmware +9 2020-04-28 medium5.3 CVE-2011-4538 Lexmark X, W, T, E, and C devices before 2012-02-09 allow attackers to obtain sensitive information by reading passwords within exported settings. lexmark · x860_firmware, lexmark · x862_firmware, lexmark · x864_firmware +9 2020-03-09 medium5.4 CVE-2019-19773 Various Lexmark products have stored XSS in the embedded web server used in older generation Lexmark devices. lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cs51x_firmware +9 2020-03-06 medium5.4 CVE-2019-19772 Various Lexmark products have reflected XSS in the embedded web server used in older generation Lexmark devices. lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cs51x_firmware +9 2020-03-06 medium5.4 CVE-2019-18791 Lexmark printer MS812 and multiple older generation Lexmark devices have a stored XSS vulnerability in the embedded web server. lexmark · cx31x_firmware, lexmark · cx41x_firmware, lexmark · cx310_firmware +9 2020-02-13 medium5.3 CVE-2019-10059 The legacy finger service (TCP port 79) is enabled by default on various older Lexmark devices. lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cx310_firmware +9 2019-08-28 medium6.5 CVE-2019-10057 Various Lexmark products have CSRF. lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cx310_firmware +9 2019-08-28 medium5.3 CVE-2019-9935 Various Lexmark products have Incorrect Access Control (issue 2 of 2). lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cx310_firmware +9 2019-08-28 medium5.3 CVE-2019-9934 Various Lexmark products have Incorrect Access Control (issue 1 of 2). lexmark · cs31x_firmware, lexmark · cs41x_firmware, lexmark · cx310_firmware +9 2019-08-28 medium4.9 CVE-2018-17944 On certain Lexmark devices that communicate with an LDAP or SMTP server, a malicious administrator can discover LDAP or SMTP credentials by changing that serve… lexmark · cx725h_firmware, lexmark · cx820_firmware, lexmark · cx825_firmware +5 2019-03-12 medium5.3 CVE-2019-6489 Certain Lexmark CX, MX, X, XC, XM, XS, and 6500e devices before 2019-02-11 allow remote attackers to erase stored shortcuts. lexmark · xm5163_firmware, lexmark · xm5170_firmware, lexmark · xm7155_firmware +9 2019-02-11 medium4.3 CVE-2017-2806 An exploitable arbitrary read exists in the XLS parsing of the Lexmark Perspective Document Filters conversion functionality. lexmark · perceptive_document_filters 2017-04-20 medium4.6 CVE-2016-3145 Lexmark printers with firmware ATL before ATL.021.063, CB before CB.021.063, PP before PP.021.063, and YK before YK.021.063 mishandle Erase Printer Memory and … lexmark · printer_firmware 2016-04-22 medium5.0 CVE-2010-0618 The flood-protection feature in the base, IPDS DLE, Forms DLE, Barcode DLE, Prescribe DLE, and Printcryption DLE components on certain Lexmark laser and inkjet… lexmark · z2420 2010-03-24 medium5.0 CVE-2004-0740 The HTTP server in Lexmark T522 and possibly other models allows remote attackers to cause a denial of service (server crash, reload, or hang) via an HTTP head… lexmark · t522_network_printer 2004-07-27

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.