NetSight

Security Dashboard

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

Reset
198 matching advisories · page 5 of 7Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.9 CVE-2026-42611 Grav is Vulnerable to Stored XSS via Tag Injection composer · getgrav/grav 2026-05-05 medium6.5 CVE-2026-56701 Grav before 2.0.0-beta.2 contains an XML external entity injection vulnerability in SVG file upload processing that allows authenticated attackers to read arbi… composer · getgrav/grav 2026-05-05 critical9.1 CVE-2026-42608 Grav has Unauthenticated Path Traversal & Arbitrary File Write in its FormFlash component composer · getgrav/grav 2026-05-05 high8.1 CVE-2026-42609 Grav Vulnerable to Administrative Account Disruption and Privilege De-escalation via User Overwrite Logic composer · getgrav/grav 2026-05-05 critical GHSA-vj3m-2g9h-vm4p Grav has multiple RCE vectors: unsafe unserialize (x3), command injection in git clone, SSTI blocklist bypass composer · getgrav/grav 2026-05-05 high8.5 CVE-2026-42612 Grav Vulnerable to Publisher-Level Stored XSS via Unquoted Event Attributes composer · getgrav/grav 2026-05-05 medium6.5 CVE-2026-42610 Grav Vulnerable to Sensitive Information Disclosure via Accounts Service Bypass composer · getgrav/grav 2026-05-05 critical9.4 CVE-2026-42613 Grav Vulnerable to Privilege Escalation via Missing Server-Side Validation of groups/access composer · getgrav/grav 2026-05-05 medium5.4 CVE-2026-42842 The form plugin for Grav adds the ability to create and use forms. composer · getgrav/grav 2026-05-05 medium4.8 CVE-2026-42841 Grav CMS vulnerable to stored XSS via Markdown media attribute() action composer · getgrav/grav 2026-05-05 critical9.1 CVE-2026-42607 Grav Vulnerable to Remote Code Execution (RCE) via Malicious Plugin ZIP Upload in Direct Install Feature composer · getgrav/grav 2026-05-05 high8.8 CVE-2026-42843 Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site's content, media, configuration, users, and system management. composer · getgrav/grav-plugin-api 2026-05-05 low5.0 GHSA-j7rw-325j-2rmx Duplicate Advisory: Grav has Insecure Deserialization in File Cache composer · getgrav/grav 2026-04-29 medium5.0 CVE-2026-7317 A vulnerability was found in Grav CMS up to 1.7.49.5/2.0.0-beta.1. composer · getgrav/grav 2026-04-28 high7.6 CVE-2026-29924 Grav CMS v1.7.x and before is vulnerable to XML External Entity (XXE) through the SVG file upload functionality in the admin panel and File Manager plugin. getgrav · grav 2026-03-30 critical9.8 CVE-2021-47812 GravCMS 1.10.7 contains an unauthenticated vulnerability that allows remote attackers to write arbitrary YAML configuration and execute PHP code through the sc… getgrav · grav 2026-01-16 critical9.1 CVE-2025-66844 Grav may be vulnerable to SSRF attack via Twig Templates composer · getgrav/grav 2025-12-15 medium5.4 CVE-2025-66843 Grav is vulnerable to Stored XSS through authenticated user-edited content composer · getgrav/grav 2025-12-15 medium6.1 CVE-2025-65186 Grav CMS is vulnerable to Cross Site Scripting (XSS) in the page editor composer · getgrav/grav 2025-12-02 medium6.2 CVE-2025-66312 Grav Admin Plugin is vulnerable to Cross-Site Scripting (XSS) Stored endpoint `/admin/accounts/groups/[group]` parameter `data[readableName]` composer · getgrav/grav 2025-12-01 medium6.2 CVE-2025-66311 Grav vulnerable to Cross-Site Scripting (XSS) Stored endpoint `/admin/pages/[page]` in Multiples parameters composer · getgrav/grav 2025-12-01 medium6.2 CVE-2025-66310 Grav vulnerable to Cross-Site Scripting (XSS) Stored endpoint `/admin/pages/[page]` parameter `data[header][template]` in Advanced Tab composer · getgrav/grav 2025-12-01 medium6.2 CVE-2025-66309 Grav is vulnerable to Cross-Site Scripting (XSS) Reflected endpoint /admin/pages/[page], parameter data[header][content][items], located in the "Blog Config" tab composer · getgrav/grav 2025-12-01 medium6.8 CVE-2025-66308 Grav Admin Plugin vulnerable to Cross-Site Scripting (XSS) Stored endpoint `/admin/config/site` parameter `data[taxonomies]` composer · getgrav/grav 2025-12-01 medium6.5 CVE-2025-66307 Grav Admin Plugin vulnerable to User Enumeration & Email Disclosure composer · getgrav/grav 2025-12-01 medium4.3 CVE-2025-66306 Grav vulnerable to Information Disclosure via IDOR in Grav Admin Panel composer · getgrav/grav 2025-12-01 high8.2 CVE-2025-66305 Grav vulnerable to Denial of Service via Improper Input Handling in 'Supported' Parameter composer · getgrav/grav 2025-12-01 medium6.2 CVE-2025-66304 Grav Exposes Password Hashes Leading to privilege escalation composer · getgrav/grav 2025-12-01 medium4.9 CVE-2025-66303 Grav is vulnerable to a DOS on the admin panel composer · getgrav/grav 2025-12-01 medium6.8 CVE-2025-66302 Grav vulnerable to Path Traversal allowing server files backup composer · getgrav/grav 2025-12-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.