NetSight

Security Dashboard

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

Reset
200 matching advisories · page 4 of 7Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.8 CVE-2026-3241 Concrete CMS has a stored Cross-site Scripting (XSS) vulnerability composer · concrete5/concrete5 2026-03-04 medium4.8 CVE-2026-3240 Concrete CMS has a stored Cross-site Scripting (XSS) vulnerability composer · concrete5/concrete5 2026-03-04 medium6.8 CVE-2026-2994 Concrete CMS vulnerable to Cross-Site Request Forgery (CSRF) composer · concrete5/concrete5 2026-03-04 high8.9 CVE-2026-3452 Concrete CMS vulnerable to Remote Code Execution by stored PHP object injection composer · concrete5/concrete5 2026-03-04 medium4.8 CVE-2026-3244 Concrete CMS has a stored Cross-site Scripting (XSS) vulnerability composer · concrete5/concrete5 2026-03-04 medium4.8 CVE-2025-8573 Concrete CMS is vulnerable to Stored XSS from Home Folder on Members Dashboard page composer · concrete5/concrete5 2025-08-05 medium4.8 CVE-2025-8571 Concrete CMS vulnerable to Reflected Cross-Site Scripting (XSS) in Conversation Messages Dashboard Page composer · concrete5/concrete5 2025-08-05 medium5.1 CVE-2025-3153 Concrete CMS Vulnerable to Cross-Site Request Forgery (CSRF) and Cross-Site Scripting (XSS) composer · concrete5/concrete5 2025-04-03 medium3.5 CVE-2025-2967 ConcreteCMS Cross-Site Scripting (XSS) via HTML Block Text Field composer · concrete5/concrete5 2025-03-31 medium4.8 CVE-2025-0660 Concrete CMS affected by a stored XSS in Folder Function.The "Add Folder" functionality composer · concrete5/concrete5 2025-03-10 medium4.8 CVE-2024-8291 Cross site scripting in Concrete CMS composer · concrete5/concrete5 2024-09-25 medium5.4 CVE-2024-7398 Cross site scripting in Concrete CMS composer · concrete5/concrete5 2024-09-25 medium4.8 CVE-2024-8660 Concrete CMS stored XSS vulnerability in the "Top Navigator Bar" block composer · concrete5/concrete5 2024-09-17 medium2.4 CVE-2024-8661 Concrete CMS Stored XSS in the "Next&Previous Nav" block composer · concrete5/concrete5 2024-09-16 medium4.8 CVE-2024-7512 Concrete CMS vulnerable to Stored Cross-site Scripting composer · concrete5/concrete5 2024-08-12 medium3.0 CVE-2024-4350 Concrete CMS Stored Cross-site Scripting vulnerability composer · concrete5/concrete5 2024-08-12 medium2.0 CVE-2024-7394 Concrete CMS Stored XSS in getAttributeSetName composer · concrete5/concrete5 2024-08-08 medium3.1 CVE-2024-4353 Concrete CMS vulnerable to Stored Cross-site Scripting composer · concrete5/concrete5 2024-08-01 low3.1 CVE-2024-3181 Concrete CMS Stored XSS in the Search Field composer · concrete5/concrete5 2024-04-03 low3.1 CVE-2024-3180 Concrete CMS Stored XSS in blocks of type file composer · concrete5/concrete5 2024-04-03 low3.1 CVE-2024-3179 Concrete CMS Stored XSS in the Custom Class page editing composer · concrete5/concrete5 2024-04-03 low3.1 CVE-2024-3178 Concrete CMS Cross-site Scripting (XSS) in the Advanced File Search Filter composer · concrete5/concrete5 2024-04-03 low2.0 CVE-2024-2753 Concrete CMS Stored XSS on the calendar color settings screen composer · concrete5/concrete5 2024-04-03 low2.2 CVE-2024-2179 Concrete CMS Stored Cross-site Scripting vulnerability composer · concrete5/concrete5 2024-03-05 low2.4 CVE-2023-49337 Concrete CMS Stored XSS composer · concrete5/concrete5 2024-02-29 medium4.3 CVE-2023-48653 Concrete CMS Cross Site Request Forgery (CSRF) vulnerability composer · concrete5/concrete5 2024-02-29 medium4.3 CVE-2023-48651 Concrete CMS Cross Site Request Forgery (CSRF) vulnerability composer · concrete5/concrete5 2024-02-29 medium4.8 CVE-2023-48650 Concrete CMS Stored XSS in Layout Preset Name composer · concrete5/concrete5 2024-02-29 low2.0 CVE-2024-1246 Concrete CMS vulnerable to reflected XSS via the Image URL Import Feature composer · concrete5/concrete5 2024-02-09 low2.4 CVE-2024-1245 Concrete CMS vulnerable to stored XSS in file tags and description attributes composer · concrete5/concrete5 2024-02-09

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.