NetSight

Security Dashboard

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

Reset
37 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2026-48191 An incorrect handling of permissions in STORM powered by OTRS and in OTRS (2026.x and above) Document Search Article Meta Filters modules allows gaining knowle… otrs · otrs 2026-06-01 low3.5 CVE-2026-48190 An incorrect handling of permissions in OTRS External Interface and the ConfigItem List module allows an authenticated customer to query the system for CI info… otrs · otrs 2026-06-01 low3.8 CVE-2025-24388 A vulnerability in the OTRS Admin Interface and Agent Interface (versions before OTRS 8) allow parameter injection due to for an autheniticated agent or admin … 2025-06-16 low3.5 CVE-2024-43446 An improper privilege management vulnerability in OTRS Generic Interface module allows change of the Ticket status even if the user only has ro permissions. 2025-01-27 low3.5 CVE-2024-23790 Improper Input Validation vulnerability in the upload functionality for user avatars allows functionality misuse due to missing check of filetypes. otrs · otrs 2024-01-29 low3.5 CVE-2023-5421 An attacker who is logged into OTRS as an user with privileges to create and change customer user data may manipulate the CustomerID field to execute JavaScrip… otrs · otrs 2023-10-16 low3.5 CVE-2022-3501 Article template contents with sensitive data could be accessed from agents without permissions. otrs · otrs 2022-10-17 low3.5 CVE-2022-39049 An attacker who is logged into OTRS as an admin user may manipulate the URL to cause execution of JavaScript in the context of OTRS. otrs · otrs 2022-09-05 low3.5 CVE-2022-32740 A reply to a forwarded email article by a 3rd party could unintensionally expose the email content to the ticket customer under certain circumstances. otrs · otrs 2022-06-13 low3.5 CVE-2022-32739 When Secure::DisableBanner system configuration has been disabled and agent shares his calendar via public URL, received ICS file contains OTRS release number. otrs · calendar_resource_planning, otrs · otrs 2022-06-13 low3.5 CVE-2022-0475 Malicious translator is able to inject JavaScript code in few translatable strings (where HTML is allowed). otrs · otrs 2022-03-21 low2.4 CVE-2022-0474 Full list of recipients from customer users in a contact field could be disclosed in notification emails event when the notification is set to be sent to each … otrs · custom_contact_fields 2022-02-07 low3.8 CVE-2022-0473 OTRS administrators can configure dynamic field and inject malicious JavaScript code in the error message of the regular expression check. otrs · otrs 2022-02-07 low3.5 CVE-2021-36097 Agents are able to lock the ticket without the "Owner" permission. otrs · otrs 2021-10-18 low3.5 CVE-2021-36091 Agents are able to list appointments in the calendars without required permissions. otrs · otrs 2021-07-26 low3.5 CVE-2021-21443 Agents are able to list customer user emails without required permissions in the bulk action screen. otrs · otrs 2021-07-26 low3.5 CVE-2021-21438 Agents are able to see linked FAQ articles without permissions (defined in FAQ Category). otrs · faq, otrs · otrs 2021-03-22 low3.5 CVE-2021-21437 Agents are able to see linked Config Items without permissions, which are defined in General Catalog. otrs · itsmconfigurationmanagement, otrs · otrscisincustomerfrontend 2021-03-22 low3.5 CVE-2021-21436 Agents are able to see and link Config Items without permissions, which are defined in General Catalog. otrs · cis_in_customer_frontend 2021-02-08 low3.5 CVE-2021-21434 Survey administrator can craft a survey in such way that malicious code can be executed in the agent interface (i.e. otrs · survey 2021-02-08 low3.5 CVE-2020-1776 When an agent user is renamed or set to invalid the session belonging to the user is keept active. otrs · otrs 2020-07-20 low3.5 CVE-2020-1775 BCC recipients in mails sent from OTRS are visible in article detail on external interface. otrs · otrs 2020-06-08 low2.4 CVE-2020-1770 Support bundle generated files could contain sensitive information that might be unwanted to be disclosed. otrs · otrs, opensuse · backports_sle, opensuse · leap +1 2020-03-27 low3.5 CVE-2020-1769 In the login screens (in agent and customer interface), Username and Password fields use autocomplete, which might be considered as security issue. otrs · otrs, opensuse · backports_sle, opensuse · leap 2020-03-27 low3.5 CVE-2020-1767 Agent A is able to save a draft (i.e. otrs · otrs, debian · debian_linux 2020-01-10 low2.0 CVE-2020-1766 Due to improper handling of uploaded images it is possible in very unlikely and rare conditions to force the agents browser to execute malicious javascript fro… otrs · otrs, debian · debian_linux 2020-01-10 low3.5 CVE-2020-1765 An improper control of parameters allows the spoofing of the from fields of the following screens: AgentTicketCompose, AgentTicketForward, AgentTicketBounce an… otrs · otrs, debian · debian_linux, opensuse · backports_sle +1 2020-01-10 low3.5 CVE-2019-9753 An issue was discovered in Open Ticket Request System (OTRS) 7.x before 7.0.5. otrs · otrs 2019-06-03 low3.5 CVE-2014-2553 Cross-site scripting (XSS) vulnerability in Open Ticket Request System (OTRS) 3.1.x before 3.1.21, 3.2.x before 3.2.16, and 3.3.x before 3.3.6 allows remote au… otrs · otrs 2014-04-02 low2.6 CVE-2012-4600 Cross-site scripting (XSS) vulnerability in Open Ticket Request System (OTRS) Help Desk 2.4.x before 2.4.14, 3.0.x before 3.0.16, and 3.1.x before 3.1.10, when… otrs · otrs, otrs · otrs_itsm 2012-08-31

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.