NetSight

Security Dashboard

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

Reset
78 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2022-3242 Microweber Cross-site Scripting can result in redirection to a malicious site composer · microweber/microweber 2022-09-20 medium6.6 CVE-2022-2777 Microweber's title parameter in the body of POST request vulnerable to stored XSS composer · microweber/microweber 2022-08-11 medium6.1 CVE-2022-2470 Microweber before 1.2.21 vulnerable to reflected XSS composer · microweber/microweber 2022-07-22 medium4.8 CVE-2022-2495 Microweber Stored Cross-site Scripting before v1.2.20 composer · microweber/microweber 2022-07-22 medium6.5 CVE-2022-2368 Microweber before 1.2.21 allows attacker to bypass IP detection to brute-force password composer · microweber/microweber 2022-07-11 medium6.3 CVE-2022-2353 Microweber before v1.2.20 vulnerable to cross-site scripting composer · microweber/microweber 2022-07-09 medium5.4 CVE-2022-2300 Cross-site Scripting in microweber composer · microweber/microweber 2022-07-04 medium5.4 CVE-2022-2280 Cross-site Scripting in microweber composer · microweber/microweber 2022-07-01 medium6.1 CVE-2022-2252 Open Redirect in microweber composer · microweber/microweber 2022-06-29 medium6.1 CVE-2022-2174 Cross-site Scripting in Microweber composer · microweber/microweber 2022-06-22 medium6.1 CVE-2022-2130 Cross-site Scripting in Microweber composer · microweber/microweber 2022-06-20 medium6.3 CVE-2022-1584 Cross-site Scripting in Microweber composer · microweber/microweber 2022-05-04 medium6.1 CVE-2022-1555 Microweber vulnerable to cross-site scripting (XSS) composer · microweber/microweber 2022-05-04 medium6.3 CVE-2022-1504 Cross-site Scripting in microweber composer · microweber/microweber 2022-04-27 medium6.3 CVE-2022-1439 Cross-site Scripting in Microweber composer · microweber/microweber 2022-04-22 medium5.4 CVE-2022-0963 Unrestricted XML files leading to cross-site scripting in Microweber composer · microweber/microweber 2022-03-15 medium6.8 CVE-2022-0954 Stored Cross-site Scripting in Microweber composer · microweber/microweber 2022-03-15 medium6.8 CVE-2022-0929 Cross-site Scripting in microweber composer · microweber/microweber 2022-03-12 medium4.8 CVE-2022-0926 Cross-site Scripting in microweber composer · microweber/microweber 2022-03-12 medium6.7 CVE-2022-0921 Unrestricted Upload of File with Dangerous Type in Microweber composer · microweber/microweber 2022-03-11 medium6.8 CVE-2022-0928 Cross-site Scripting in microweber composer · microweber/microweber 2022-03-11 medium4.8 CVE-2022-0912 Unrestricted Upload of File with Dangerous Type in microweber composer · microweber/microweber 2022-03-11 medium4.8 CVE-2022-0906 Unrestricted file upload leads to stored cross-site scripting in Microweber composer · microweber/microweber 2022-03-10 medium6.1 CVE-2022-0855 Improper Resolution of Path Equivalence in GitHub repository microweber-dev/whmcs_plugin prior to 0.0.4. microweber · whmcs 2022-03-04 medium5.4 CVE-2022-0723 Cross-site Scripting in microweber composer · microweber/microweber 2022-02-26 medium4.8 CVE-2022-0763 Cross-site Scripting in microweber composer · microweber/microweber 2022-02-26 medium4.3 CVE-2022-0762 Exposure of Resource to Wrong Sphere in microweber composer · microweber/microweber 2022-02-26 medium4.9 CVE-2022-0688 Business Logic Errors in microweber composer · microweber/microweber 2022-02-20 medium5.3 CVE-2022-0689 Business Logic Errors in microweber composer · microweber/microweber 2022-02-19 medium6.5 CVE-2022-0678 Cross-site Scripting in microweber composer · microweber/microweber 2022-02-19

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.