NetSight

Security Dashboard

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

Reset
18 matching advisories · page 1 of 1Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.3 CVE-2026-129408 Joomla Extension - vi-solutions - Stored XSS via SQL field labels in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Labels and values of SQL field options were … vi-solutions · Visforms extension for Joomla 2 days ago low2.1 CVE-2026-129401 Joomla Extension - vi-solutions - Open redirect on invalid form submission in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The return parameter of an invalid … vi-solutions · Visforms extension for Joomla 2 days ago low2.1 CVE-2026-129409 Joomla Extension - vi-solutions - Open redirects in data view controller and after form submission in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Return and … vi-solutions · Visforms extension for Joomla 2 days ago low3.8 CVE-2026-92223 Joomla! joomla · joomla\! 53 days ago low2.7 CVE-2026-90916 Joomla! joomla · joomla\! 53 days ago low3.4 CVE-2026-48940 A Joomla user with K2 "create item" rights (Author tier by default) can submit an article whose `embedVideo` POST field contains a raw `<script>` tag; K2 store… joomlaworks · k2 2026-06-25 low3.8 CVE-2025-25228 A SQL injection in VirtueMart component 1.0.0 - 4.4.7 for Joomla allows authenticated attackers (administrator) to execute arbitrary SQL commands in the produc… virtuemart · virtuemart 2025-04-21 low2.7 CVE-2025-22212 A SQL injection vulnerability in the Convert Forms component versions 1.0.0-1.0.0 - 4.4.9 for Joomla allows authenticated attackers (administrator) to execute … convert_forms_project · convert_forms 2025-03-05 low3.4 CVE-2025-22211 A SQL injection vulnerability in the JoomShopping component versions 1.0.0-1.4.3 for Joomla allows authenticated attackers (administrator) to execute arbitrary… webdesigner-profi · joomshopping 2025-02-25 low3.7 CVE-2017-14595 In Joomla! joomla · joomla\! 2017-09-20 low2.1 CVE-2014-8607 The XCloner plugin 3.1.1 for WordPress and 3.5.1 for Joomla! xcloner · xcloner 2015-06-10 low2.6 CVE-2013-5951 Multiple cross-site scripting (XSS) vulnerabilities in eXtplorer 2.1.3, when used as a component for Joomla!, allow remote attackers to inject arbitrary web sc… extplorer · extplorer 2014-03-25 low3.5 CVE-2011-4830 Multiple cross-site scripting (XSS) vulnerabilities in the com_listing component in Barter Sites component 1.3 for Joomla! barter-sites · com_listing 2011-12-15 low3.5 CVE-2010-2535 Multiple cross-site scripting (XSS) vulnerabilities in the Back End in Joomla! joomla · joomla\! 2010-10-05 low3.6 CVE-2010-3028 The Aardvertiser component before 2.2.1 for Joomla! simon_philips · aardvertiser 2010-08-16 low3.5 CVE-2010-0801 Directory traversal vulnerability in the AutartiTarot (com_autartitarot) component 1.0.3 for Joomla! autartica · com_autartitarot 2010-03-02 low2.6 CVE-2009-1279 Multiple cross-site scripting (XSS) vulnerabilities in Joomla! joomla · joomla 2009-04-09 low3.5 CVE-2008-6299 Multiple cross-site scripting (XSS) vulnerabilities in Joomla! joomla · joomla 2009-02-26

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.