NetSight

Security Dashboard

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

Reset
38 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2026-65693 Microweber CMS through 2.0.20 contains a server-side template injection vulnerability that allows authenticated administrators to achieve arbitrary OS command … Microweber CMS 2026-07-24 high7.5 CVE-2026-65694 Microweber CMS through 2.0.20 contains a path traversal vulnerability in the static file controller that allows unauthenticated remote attackers to read arbitr… Microweber CMS 2026-07-23 high7.3 CVE-2026-12198 A weakness has been identified in Microweber up to 2.0.20. composer · microweber/microweber 2026-06-15 high8.3 CVE-2025-60954 Microweber CMS 2.0 has Weak Password Requirements. microweber · microweber 2025-10-24 high7.6 CVE-2025-51504 Microweber XSS Vulnerability in the homepage Endpoint composer · microweber/microweber 2025-08-01 high7.6 CVE-2025-51503 Microweber Has Stored XSS Vulnerability in User Profile Fields composer · microweber/microweber 2025-07-31 high7.2 CVE-2025-34076 Microweber CMS API has authenticated local file inclusion vulnerability composer · microweber/microweber 2025-07-02 high7.5 CVE-2023-48122 Microweber allows a remote attacker to obtain sensitive information via the HTTP GET method composer · microweber/microweber 2023-12-08 high8.8 CVE-2023-49052 Microweber file upload vulnerability composer · microweber/microweber 2023-11-30 high7.5 CVE-2023-5318 Microweber uses hard coded credentials composer · microweber/microweber 2023-09-30 high8.8 CVE-2023-2240 Improper Privilege Management in microweber composer · microweber/microweber 2023-04-22 high7.4 CVE-2023-1881 Microweber vulnerable to stored cross-site scripting (XSS) via X-Forwarded-For header composer · microweber/microweber 2023-04-05 high7.2 CVE-2022-4732 Microweber vulnerable to unrestricted malicious uploads composer · microweber/microweber 2022-12-27 high8.8 CVE-2022-33012 Account Takeover Through Password Reset Poisoning composer · microweber/microweber 2022-11-22 high8.8 CVE-2021-36461 An Arbitrary File Upload vulnerability exists in Microweber 1.1.3 that allows attackers to getshell via the Settings Upload Picture section by uploading pictur… microweber · microweber 2022-07-15 high8.8 CVE-2022-1631 Incorrect Authorization in microweber composer · microweber/microweber 2022-05-09 high7.5 CVE-2022-1036 Integer Overflow or Wraparound in Microweber composer · microweber/microweber 2022-03-22 high7.2 CVE-2022-0968 Integer Overflow in microweber composer · microweber/microweber 2022-03-15 high7.1 CVE-2022-0961 Denial of service in microweber composer · microweber/microweber 2022-03-15 high4.8 CVE-2022-0930 Cross-site Scripting in microweber composer · microweber/microweber 2022-03-12 high7.5 CVE-2022-0913 Integer Overflow or Wraparound in Microweber composer · microweber/microweber 2022-03-11 high8.8 CVE-2022-0896 Improper Neutralization of Special Elements Used in a Template Engine in microweber composer · microweber/microweber 2022-03-09 high7.5 CVE-2022-0777 Rate limit missing in microweber composer · microweber/microweber 2022-03-01 high6.5 CVE-2022-0724 Insecure Storage of Sensitive Information in Microweber composer · microweber/microweber 2022-02-23 high8.8 CVE-2022-0721 Insertion of Sensitive Information Into Debugging Code in Microweber composer · microweber/microweber 2022-02-23 high7.6 CVE-2022-0719 Cross-site Scripting in Microweber composer · microweber/microweber 2022-02-23 high8.8 CVE-2022-0690 Cross-site Scripting in microweber composer · microweber/microweber 2022-02-19 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 high7.8 CVE-2022-0557 OS Command Injection in Microweber composer · microweber/microweber 2022-02-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.