NetSight

Security Dashboard

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

Reset
98 matching advisories · page 3 of 4Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.8 CVE-2026-25484 Craft Commerce has Stored XSS in Product Type Name composer · craftcms/commerce 2026-02-02 medium6.2 CVE-2026-25483 Craft Commerce has Stored XSS via Order Status Message with potential database exfiltration composer · craftcms/commerce 2026-02-02 medium6.2 CVE-2026-25482 Craft Commerce has Stored DOM XSS in Order Status Name (Reflects in "Recent Orders" Dashboard Widget) composer · craftcms/commerce 2026-02-02 medium5.0 CVE-2025-68437 Craft CMS vulnerable to Server-Side Request Forgery (SSRF) via GraphQL Asset Upload Mutation composer · craftcms/cms 2026-01-05 medium4.9 CVE-2025-68436 Craft CMS vulnerable to potential information disclosure via unchecked asset relocation composer · craftcms/cms 2026-01-05 medium5.3 CVE-2025-35939 Craft CMS stores arbitrary content provided by unauthenticated users in session filesExploited composer · craftcms/cms 2025-05-07 medium5.5 CVE-2024-45406 Craft CMS vulnerable to stored XSS in breadcrumb list and title fields composer · craftcms/cms 2024-09-09 medium4.8 CVE-2024-41800 Craft CMS Allows TOTP Token To Stay Valid After Use composer · craftcms/cms 2024-07-25 medium4.8 CVE-2024-5658 The CraftCMS plugin Two-Factor Authentication through 3.3.3 allows reuse of TOTP tokens multiple times within the validity period. composer · born05/craft-twofactorauthentication 2024-06-06 medium5.4 CVE-2023-36259 Craft CMS Audit Plugin Cross Site Scripting vulnerability composer · superbig/craft-audit 2024-01-30 medium5.4 CVE-2024-21622 Craft CMS Privilege Escalation composer · craftcms/cms 2024-01-03 medium6.1 CVE-2023-33495 Craft CMS vulnerable to HTML injection composer · craftcms/cms 2023-06-20 medium5.4 CVE-2023-2817 Stored cross site scripting in Craft CMS composer · craftcms/cms 2023-05-26 medium5.5 CVE-2023-33197 Craft CMS stored XSS in indexedVolumes composer · craftcms/cms 2023-05-26 medium5.5 CVE-2023-33196 Craft CMS stored XSS in review volume composer · craftcms/cms 2023-05-26 medium6.1 CVE-2023-33195 Craft CMS XSS in RSS widget feed composer · craftcms/cms 2023-05-26 medium6.1 CVE-2023-31144 craftcms/cms vulnerable to cross site scripting in RSS feed widget composer · craftcms/cms 2023-05-05 medium6.1 CVE-2023-30177 CraftCMS 3.7.59 is vulnerable Cross Site Scripting (XSS). composer · craftcms/cms 2023-04-25 medium6.1 CVE-2023-23927 Craft CMS Stored Cross-site Scripting Injection Vulnerability composer · craftcms/cms 2023-03-03 medium5.4 CVE-2022-37246 Craft CMS Cross-site Scripting vulnerability composer · craftcms/cms 2022-09-21 medium5.4 CVE-2022-37251 Craft CMS vulnerable to Cross-site Scripting via entry revisions and drafts composer · craftcms/cms 2022-09-16 medium5.4 CVE-2022-37247 Craft CMS vulnerable to stored Cross-site Scripting via /admin/settings/fields page composer · craftcms/cms 2022-09-16 medium5.4 CVE-2022-37248 Craft CMS Cross site Scripting vulnerability composer · craftcms/cms 2022-09-16 medium5.4 CVE-2022-37250 Craft CMS Stored Cross-site Scripting in User Addresses Title composer · craftcms/cms 2022-09-16 medium6.1 CVE-2022-28378 Cross-site Scripting in craftcms/cms composer · craftcms/cms 2022-04-03 medium6.1 CVE-2021-27902 Craft CMS Cross-site Scripting Vulnerability composer · craftcms/cms 2021-06-30 medium6.1 CVE-2021-32470 Craft CMS Cross-site Scripting Vulnerability composer · craftcms/cms 2021-05-07 medium5.4 CVE-2020-19626 Cross Site Scripting (XSS) vulnerability in craftcms 3.1.31, allows remote attackers to inject arbitrary web script or HTML, via /admin/settings/sites/new. composer · craftcms/cms 2021-03-26 medium6.1 CVE-2019-9554 In the 3.1.12 Pro version of Craft CMS, XSS has been discovered in the header insertion field when adding source code at an s/admin/entries/news/new URI. craftcms · craft_cms 2019-12-31 medium6.1 CVE-2019-17496 Craft CMS XSS Vulnerability composer · craftcms/cms 2019-10-11

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.