NetSight

Security Dashboard

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

Reset
441 matching advisories · page 5 of 15Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2025-68388 Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments go · github.com/elastic/beats, go · github.com/elastic/beats/v7 2025-12-18 high8.1 CVE-2025-53446 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in axiomthemes Beautique beautique allows… axiomthemes · beautique 2025-12-18 high7.1 CVE-2025-68254 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing The Extended Supporte… 2025-12-16 high7.5 CVE-2025-41738 An unauthenticated remote attacker may cause the visualisation server of the CODESYS Control runtime system to access a resource with a pointer of wrong type, … codesys · control_for_beaglebone_sl, codesys · control_for_empc-a\/imx6_sl, codesys · control_for_iot2000_sl +9 2025-12-01 high8.8 CVE-2025-54719 Deserialization of Untrusted Data vulnerability in NooTheme Yogi - Health Beauty & Yoga noo-yogi allows Object Injection.This issue affects Yogi - Health Beaut… Yogi - Health Beauty & Yoga: from n/a through 2025-11-06 high7.1 CVE-2025-54718 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in NooTheme Yogi - Health Beauty & Yoga noo-yogi allows Refl… Yogi - Health Beauty & Yoga: from n/a through 2025-11-06 high7.3 CVE-2025-11507 A weakness has been identified in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-10-08 high7.3 CVE-2025-11506 A security flaw has been discovered in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-10-08 high7.3 CVE-2025-11505 A vulnerability was identified in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-10-08 high7.3 CVE-2025-11503 A vulnerability was determined in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-10-08 high7.3 CVE-2025-11416 A security flaw has been discovered in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-10-07 high7.3 CVE-2025-11415 A vulnerability was identified in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-10-07 high8.2 CVE-2025-57564 CubeAPM nightly-2025-08-01-1 allow unauthenticated attackers to inject arbitrary log entries into production systems via the /api/logs/insert/elasticsearch/_bu… 2025-10-07 high7.3 CVE-2025-10459 A security flaw has been discovered in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-15 high7.3 CVE-2025-10403 A vulnerability has been found in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-14 high7.3 CVE-2025-10402 A flaw has been found in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-14 high8.8 CVE-2025-48208 Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability in Apache HertzBeat . apache · hertzbeat 2025-09-09 high8.8 CVE-2025-24404 XML Injection RCE by parse http sitemap xml response vulnerability in Apache HertzBeat. apache · hertzbeat 2025-09-09 high7.1 CVE-2025-53307 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Beaver Builder WordPress Assistant assistant allows Refle… WordPress Assistant: from n/a through 2025-09-05 high7.3 CVE-2025-9933 A vulnerability has been found in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-04 high7.3 CVE-2025-9932 A flaw has been found in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-04 high7.3 CVE-2025-9930 A security vulnerability has been detected in 1000projects Beauty Parlour Management System 1.0. 1000projects · beauty_parlour_management_system 2025-09-04 high7.3 CVE-2025-9919 A vulnerability was identified in 1000projects Beauty Parlour Management System 1.0. 1000projects · beauty_parlour_management_system 2025-09-03 high7.3 CVE-2025-9831 A weakness has been identified in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-02 high7.3 CVE-2025-9830 A security flaw has been discovered in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-02 high7.3 CVE-2025-9829 A vulnerability was identified in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-02 high7.3 CVE-2025-9814 A security flaw has been discovered in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-09-02 high7.3 CVE-2025-9024 A vulnerability was found in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-08-15 high8.8 CVE-2025-5997 Incorrect Use of Privileged APIs vulnerability in Beamsec PhishPro allows Privilege Abuse. PhishPro 2025-07-28 high7.5 CVE-2025-36512 A denial of service vulnerability exists in the Bloomberg Comdb2 8.1 database when handling a distributed transaction heartbeat. bloomberg · comdb2 2025-07-22

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.