NetSight

Security Dashboard

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

Reset
27 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.1 CVE-2026-130079 B3log Solo through 4.4.0 contains a stored cross-site scripting vulnerability that allows attackers to inject script by setting a malicious article title rende… b3log · Solo 5 days ago medium5.4 CVE-2026-111610 B3log Solo through 4.4.0 contains a missing authorization vulnerability in ArticleConsole that allows authenticated authors to access other authors' articles b… B3log Solo 36 days ago medium5.3 CVE-2026-110105 B3log Symphony through 3.6.4 contains a missing authorization vulnerability that allows unauthenticated attackers to reach admin routes because PermissionMidwa… B3log Symphony 39 days ago medium5.4 CVE-2026-40922 SiYuan is an open-source personal knowledge management system. go · github.com/siyuan-note/siyuan/kernel 2026-04-14 medium6.8 CVE-2026-33194 SiYuan has an Incomplete Fix for IsSensitivePath Denylist Allows File Read from /opt, /usr, /home (GHSA-h5vh-m7fg-w5h6 Bypass) go · github.com/siyuan-note/siyuan/kernel 2026-03-18 medium6.8 CVE-2026-32750 SiYuan importStdMd: unvalidated localPath imports arbitrary host directories as persistent notes go · github.com/siyuan-note/siyuan 2026-03-16 medium6.8 CVE-2026-32747 SiYuan globalCopyFiles: incomplete sensitive path blocklist allows reading /proc and Docker secrets go · github.com/siyuan-note/siyuan/kernel 2026-03-16 medium6.5 CVE-2026-32704 SiYuan's renderSprig has a missing admin check that allows any user to read full workspace DB go · github.com/siyuan-note/siyuan/kernel 2026-03-13 medium6.4 CVE-2026-31809 SiYuan has a SVG Sanitizer Bypass via Whitespace in `javascript:` URI — Unauthenticated XSS go · github.com/siyuan-note/siyuan/kernel 2026-03-10 medium6.4 CVE-2026-31807 SiYuan has a SVG Sanitizer Bypass via `<animate>` Element — Unauthenticated XSS go · github.com/siyuan-note/siyuan/kernel 2026-03-10 medium4.6 CVE-2026-25647 Lute is a structured Markdown engine supporting Go and JavaScript. b3log · siyuan 2026-02-06 medium6.1 CVE-2026-23847 SiYuan has a Reflected Cross-Site Scripting (XSS) via /api/icon/getDynamicIcon go · github.com/siyuan-note/siyuan/kernel 2026-01-19 medium5.3 CVE-2026-23645 SiYuan Has a Stored Cross-Site Scripting (XSS) Vulnerability via Unrestricted SVG File Upload go · github.com/siyuan-note/siyuan/kernel 2026-01-16 medium5.9 CVE-2024-39150 vditor v.3.9.8 and before is vulnerable to Arbitrary file read via a crafted data packet. b3log · vditor 2024-07-05 medium6.1 CVE-2024-34449 Vditor allows Cross-site Scripting via an attribute of an `A` element npm · vditor 2024-05-03 medium6.1 CVE-2021-32855 Vditor Cross-site Scripting vulnerability npm · vditor 2023-02-21 medium5.4 CVE-2022-0350 Cross-site Scripting in vditor npm · vditor 2022-03-31 medium5.4 CVE-2022-0341 Cross-site Scripting in vditor npm · vditor 2022-03-14 medium5.4 CVE-2021-4103 vditor Vulnerable to Cross-site Scripting in SVG events npm · vditor 2022-01-23 medium6.1 CVE-2019-17488 b3log Symphony (aka Sym) before 3.6.0 has XSS via the HTTP User-Agent header. b3log · symphony 2019-10-10 medium6.1 CVE-2018-16248 b3log Solo 2.9.3 has XSS in the Input page under the "Publish Articles" menu with an ID of "articleTags" stored in the "tag" JSON field, which allows remote at… b3log · solo 2019-06-20 medium4.8 CVE-2018-16249 In Symphony before 3.3.0, there is XSS in the Title under Post. b3log · symphony 2019-06-20 medium6.1 CVE-2019-9142 Moderate severity vulnerability that affects org.b3log:symphony maven · org.b3log:symphony 2019-02-25 medium4.8 CVE-2018-16805 In b3log Solo 2.9.3, XSS in the Input page under the Publish Articles menu, with an ID of linkAddress stored in the link JSON field, allows remote attackers to… b3log · solo 2018-09-10 medium6.1 CVE-2017-16956 b3log Symphony (aka Sym) 2.2.0 allows an XSS attack by sending a private letter with a certain /article URI, and a second private letter with a modified title. symphony_project · symphony 2017-11-27 medium6.1 CVE-2017-16881 b3log Symphony (aka Sym) 2.2.0 does not properly address XSS in JSON objects, as demonstrated by a crafted userAvatarURL value to /settings/avatar, related to … symphony_project · symphony 2017-11-18 medium5.4 CVE-2017-16821 b3log Symphony (aka Sym) 2.2.0 has XSS in processor/AdminProcessor.java in the admin console, as demonstrated by a crafted X-Forwarded-For HTTP header that is … b3log · symphony 2017-11-15

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.