NetSight

Security Dashboard

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

Reset
120 matching advisories · page 4 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.6 CVE-2022-0666 CRLF Injection in microweber composer · microweber/microweber 2022-02-18 high7.5 CVE-2022-0660 Generation of Error Message Containing Sensitive Information in microweber composer · microweber/microweber 2022-02-18 medium4.3 CVE-2022-0638 Cross-Site Request Forgery microweber composer · microweber/microweber 2022-02-17 medium6.1 CVE-2022-0597 Open redirect in microweber composer · microweber/microweber 2022-02-15 medium4.3 CVE-2022-0596 Microweber vulnerable to Improper Validation of Specified Quantity in Input composer · microweber/microweber 2022-02-15 medium6.1 CVE-2022-0560 Open redirect in microweber composer · microweber/microweber 2022-02-11 high7.8 CVE-2022-0557 OS Command Injection in Microweber composer · microweber/microweber 2022-02-11 medium5.4 CVE-2022-0558 Cross-site Scripting in microweber composer · microweber/microweber 2022-02-10 medium5.4 CVE-2022-0506 Cross-site Scripting in microweber composer · microweber/microweber 2022-02-08 medium6.5 CVE-2022-0505 Cross-Site Request Forgery in microweber composer · microweber/microweber 2022-02-08 medium6.5 CVE-2022-0504 Generation of Error Message Containing Sensitive Information in microweber composer · microweber/microweber 2022-02-08 medium5.4 CVE-2022-0379 Cross-site Scripting in microweber composer · microweber/microweber 2022-01-26 medium5.4 CVE-2022-0378 Cross-site Scripting in microweber composer · microweber/microweber 2022-01-26 high7.5 CVE-2022-0282 Code Injection in microweber composer · microweber/microweber 2022-01-20 high7.5 CVE-2022-0281 Exposure of Sensitive Information to an Unauthorized Actor in microweber composer · microweber/microweber 2022-01-20 medium5.4 CVE-2022-0278 Cross-site Scripting in microweber composer · microweber/microweber 2022-01-20 medium6.5 CVE-2022-0277 Microweber Incorrect Permission Assignment for Critical Resource vulnerability composer · microweber/microweber 2022-01-20 medium6.1 CVE-2021-33988 Cross Site Scripting in Microweber composer · microweber/microweber 2021-10-19 high7.2 CVE-2020-28337 Zip slip in Microweber composer · microweber/microweber 2021-02-15 high8.1 CVE-2020-23140 Microweber 1.1.18 is affected by insufficient session expiration. microweber · microweber 2020-11-09 medium5.5 CVE-2020-23139 Microweber 1.1.18 is affected by broken authentication and session management. microweber · microweber 2020-11-09 critical9.8 CVE-2020-23138 An unrestricted file upload vulnerability was discovered in the Microweber 1.1.18 admin account page. microweber · microweber 2020-11-09 medium5.5 CVE-2020-23136 Microweber Insufficient Session Expiry composer · microweber/microweber 2020-11-09 high7.5 CVE-2020-13405 Microweber Discloses Sensitive Information composer · microweber/microweber 2020-07-16 high7.8 CVE-2020-13241 Microweber allows Unrestricted File Upload composer · microweber/microweber 2020-05-20 medium6.1 CVE-2018-19917 Microweber XSS Vulnerability composer · microweber/microweber 2019-03-21 medium6.1 CVE-2018-1000826 Microweber XSS Vulnerability composer · microweber/microweber 2018-12-20 high8.8 CVE-2018-17104 An issue was discovered in Microweber 1.0.7. microweber · microweber 2018-09-16 high7.5 CVE-2014-9464 SQL injection vulnerability in Category.php in Microweber CMS 0.95 before 20141209 allows remote attackers to execute arbitrary SQL commands via the category p… microweber · microweber 2015-01-03 medium6.4 CVE-2013-5984 Directory traversal vulnerability in userfiles/modules/admin/backup/delete.php in Microweber before 0.830 allows remote attackers to delete arbitrary files via… microweber · microweber 2014-05-12

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.