NetSight

Security Dashboard

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

Reset
43 matching advisories · page 1 of 2Index updated 5 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-27954 Live Helper Chat is an open-source application that enables live support websites. livehelperchat · live_helper_chat 2026-02-26 medium6.5 CVE-2025-51403 A stored cross-site scripting (XSS) vulnerability in the department assignment editing module of of Live Helper Chat v4.60 allows attackers to execute arbitrar… livehelperchat · live_helper_chat 2025-07-21 medium5.4 CVE-2025-51401 A stored cross-site scripting (XSS) vulnerability in the chat transfer function of Live Helper Chat v4.60 allows attackers to execute arbitrary web scripts or … livehelperchat · live_helper_chat 2025-07-21 medium5.4 CVE-2025-51400 A stored cross-site scripting (XSS) vulnerability in the Personal Canned Messages of Live Helper Chat v4.60 allows attackers to execute arbitrary web scripts o… livehelperchat · live_helper_chat 2025-07-21 medium5.4 CVE-2025-51398 A stored cross-site scripting (XSS) vulnerability in the Facebook registration page of Live Helper Chat v4.60 allows attackers to execute arbitrary web scripts… livehelperchat · live_helper_chat 2025-07-21 medium5.4 CVE-2025-51397 A stored cross-site scripting (XSS) vulnerability in the Facebook Chat module of Live Helper Chat v4.60 allows attackers to execute arbitrary web scripts or HT… livehelperchat · live_helper_chat 2025-07-21 medium5.4 CVE-2025-51396 A stored cross-site scripting (XSS) vulnerability in Live Helper Chat v4.60 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted p… livehelperchat · live_helper_chat 2025-07-21 low3.5 CVE-2025-7435 A vulnerability was found in LiveHelperChat lhc-php-resque Extension up to ee1270b35625f552425e32a6a3061cd54b5085c4. 2025-07-11 critical9.8 CVE-2024-27516 livehelperchat Server-Side Template Injection composer · remdex/livehelperchat 2024-02-29 medium6.1 CVE-2022-1530 An attacker can execute malicious javascript in Live Helper Chat composer · remdex/livehelperchat 2022-04-29 high8.8 CVE-2022-0935 Host Header injection in password Reset in GitHub repository livehelperchat/livehelperchat prior to 3.97. livehelperchat · live_helper_chat 2022-04-07 medium6.1 CVE-2022-1234 XSS in livehelperchat in GitHub repository livehelperchat/livehelperchat prior to 3.97. livehelperchat · live_helper_chat 2022-04-06 high7.5 CVE-2022-1235 Weak password hash in LiveHelperChat composer · remdex/livehelperchat 2022-04-05 high7.7 CVE-2022-1213 Server side request forgery in LiveHelperChat composer · remdex/livehelperchat 2022-04-05 high7.5 CVE-2022-1176 Type Confusion in LiveHelperChat composer · remdex/livehelperchat 2022-03-31 high8.1 CVE-2022-1191 SSRF on index.php/cobrowse/proxycss/ in GitHub repository livehelperchat/livehelperchat prior to 3.96. livehelperchat · live_helper_chat 2022-03-31 medium6.7 CVE-2022-0612 Cross-site Scripting in livehelperchat composer · remdex/livehelperchat 2022-02-16 medium5.4 CVE-2022-0502 Cross-site Scripting in LiveHelperChat composer · remdex/livehelperchat 2022-02-06 medium5.4 CVE-2022-0395 Cross-site Scripting in LiveHelperChat composer · remdex/livehelperchat 2022-01-28 medium5.4 CVE-2022-0394 Cross-site Scripting in LiveHelperChat composer · remdex/livehelperchat 2022-01-28 medium5.4 CVE-2022-0387 Cross-site Scripting in livehelperchat composer · remdex/livehelperchat 2022-01-27 medium5.4 CVE-2022-0370 Cross-site Scripting in livehelperchat composer · remdex/livehelperchat 2022-01-27 medium6.5 CVE-2022-0375 Cross-site Scripting in livehelperchat composer · remdex/livehelperchat 2022-01-26 medium6.5 CVE-2022-0374 Cross-site Scripting in livehelperchat composer · remdex/livehelperchat 2022-01-26 medium6.5 CVE-2022-0266 Authorization Bypass Through User-Controlled Key in LiveHelperChat composer · remdex/livehelperchat 2022-01-19 medium4.3 CVE-2022-0245 Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat composer · livehelperchat/livehelperchat 2022-01-18 medium5.4 CVE-2022-0253 livehelperchat is vulnerable to Cross-site Scripting composer · remdex/livehelperchat 2022-01-17 medium4.3 CVE-2022-0226 Cross-Site Request Forgery (CSRF) in livehelperchat composer · remdex/livehelperchat 2022-01-14 medium6.5 CVE-2022-0231 Cross-Site Request Forgery (CSRF) in livehelperchat composer · remdex/livehelperchat 2022-01-14 medium5.3 CVE-2022-0083 User enumeration in livehelperchat composer · remdex/livehelperchat 2022-01-04

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.