NetSight

Security Dashboard

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

Reset
111 matching advisories · page 4 of 4Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2022-42189 Emlog Pro 1.6.0 plugins upload suffers from a remote code execution (RCE) vulnerability. emlog · emlog 2022-10-21 medium5.4 CVE-2021-40610 Emlog Pro v 1.0.4 cross-site scripting (XSS) in Emlog Pro background management. emlog_pro_project · emlog_pro 2022-06-09 low3.5 CVE-2022-1526 A vulnerability, which was classified as problematic, was found in Emlog Pro up to 1.2.2. emlog · emlog 2022-04-29 critical9.8 CVE-2022-23379 Emlog v6.0 was discovered to contain a SQL injection vulnerability via the $TagID parameter of getblogidsfromtagid(). emlog · emlog 2022-02-04 medium4.8 CVE-2022-23872 Emlog pro v1.1.1 was discovered to contain a stored cross-site scripting (XSS) vulnerability in the component /admin/configure.php via the parameter footer_inf… emlog · emlog 2022-01-31 medium6.1 CVE-2021-44584 Cross-site scripting (XSS) vulnerability in index.php in emlog version <= pro-1.0.7 allows remote attackers to inject arbitrary web script or HTML via the s pa… emlog · emlog 2022-01-06 critical9.8 CVE-2021-40883 A Remote Code Execution (RCE) vulnerability exists in emlog 5.3.1 via content/plugins. emlog · emlog 2021-12-14 high7.2 CVE-2020-21654 emlog v6.0 contains a vulnerability in the component admin\template.php, which allows attackers to getshell via a crafted Zip file. emlog · emlog 2021-10-06 medium6.5 CVE-2020-21014 emlog v6.0.0 contains an arbitrary file deletion vulnerability in admin/plugin.php. emlog · emlog 2021-10-01 high7.2 CVE-2020-21013 emlog v6.0.0 contains a SQL injection via /admin/comment.php. emlog · emlog 2021-10-01 medium4.3 CVE-2020-21321 emlog v6.0 contains a Cross-Site Request Forgery (CSRF) via /admin/link.php?action=addlink, which allows attackers to arbitrarily add articles. emlog · emlog 2021-09-15 high8.8 CVE-2021-30081 An issue was discovered in emlog 6.0.0stable. emlog · emlog 2021-05-24 medium6.1 CVE-2020-18194 Cross Site Scripting (XSS) in emlog v6.0.0 allows remote attackers to execute arbitrary code by adding a crafted script as a link to a new blog post. emlog · emlog 2021-05-17 critical9.8 CVE-2021-31737 emlog v5.3.1 and emlog v6.0.0 have a Remote Code Execution vulnerability due to upload of database backup file in admin/data.php. emlog · emlog 2021-05-06 medium6.1 CVE-2021-30227 Cross Site Scripting (XSS) vulnerability in the article comments feature in emlog 6.0. emlog · emlog 2021-04-29 critical9.8 CVE-2020-21585 Vulnerability in emlog v6.0.0 allows user to upload webshells via zip plugin module. emlog · emlog 2021-04-02 medium5.3 CVE-2021-3293 emlog v5.3.1 has full path disclosure vulnerability in t/index.php, which allows an attacker to see the path to the webroot/file. emlog · emlog 2021-02-08 medium6.5 CVE-2019-17073 emlog through 6.0.0beta allows remote authenticated users to delete arbitrary files via admin/template.php?action=del&tpl=../ directory traversal. emlog · emlog 2019-10-01 critical9.8 CVE-2019-16868 emlog through 6.0.0beta has an arbitrary file deletion vulnerability via an admin/data.php?action=dell_all_bak request with directory traversal sequences in th… emlog · emlog 2019-09-25 high8.8 CVE-2019-10660 Grandstream GXV3611IR_HD before 1.0.3.23 devices allow remote authenticated users to execute arbitrary code via shell metacharacters in the /goform/systemlog?c… grandstream · gxv3611ir_hd_firmware 2019-03-30 high8.8 CVE-2018-18316 emlog v6.0.0 has CSRF via the admin/user.php?action=new URI. emlog · emlog 2018-10-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.