NetSight

Security Dashboard

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

Reset
1,774 matching advisories · page 17 of 60Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2026-21631 Lack of output escaping leads to a XSS vector in the multilingual associations component. joomla · joomla\! 2026-04-01 high8.8 CVE-2026-21630 Improperly built order clauses lead to a SQL injection vulnerability in the articles webservice endpoint. joomla · joomla\! 2026-04-01 high7.3 CVE-2026-21629 The ajax component was excluded from the default logged-in-user check in the administrative area. joomla · joomla\! 2026-04-01 high7.1 CVE-2026-25341 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RSJoomla! RSFirewall!: from n/a through 2026-03-25 critical9.5 CVE-2026-21627 The vulnerability was rooted in how the Tassos Framework plugin handled specific AJAX requests through Joomla’s com_ajax entry point. 2026-02-20 high8.8 CVE-2026-21625 User provided uploads to the Easy Discuss component for Joomla aren't properly validated. stackideas · easydiscuss 2026-01-16 medium5.4 CVE-2026-21624 Lack of input filterung leads to a persistent XSS vulnerability in the user avatar text handling of the Easy Discuss component for Joomla. stackideas · easydiscuss 2026-01-16 medium5.4 CVE-2026-21623 Lack of input filterung leads to a persistent XSS vulnerability in the forum post handling of the Easy Discuss component for Joomla. stackideas · easydiscuss 2026-01-16 critical9.3 CVE-2025-32303 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Mojoomla WPCHURCH allows Blind SQL Injection.This issue a… WPCHURCH: from n/a 2026-01-07 high8.1 CVE-2025-32304 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mojoomla WPCHURCH allows PHP Local Fil… WPCHURCH: from n/a 2026-01-06 medium6.1 CVE-2025-63083 Lack of output escaping leads to a XSS vector in the pagebreak plugin. joomla · joomla\! 2026-01-06 medium6.1 CVE-2025-63082 Lack of input filtering leads to an XSS vector in the HTML filter code related to data URLs in img tags. joomla · joomla\! 2026-01-06 medium5.4 CVE-2025-55758 Multiple CSRF attack vectors in JDownloads component 1.0.0-4.0.47 for Joomla were discovered. 2025-10-28 medium6.1 CVE-2025-55757 A unauthenticated reflected XSS vulnerability in VirtueMart 1.0.0-4.4.10 for Joomla was discovered. 2025-10-25 critical9.3 CVE-2025-40636 SQL injection vulnerability in Joomla module mod_vvisit_counter v2.0.4j3. 2025-10-03 medium4.8 CVE-2025-54476 Joomla! CMS vulnerable to XSS via the input filter composer · joomla/filter 2025-09-30 critical9.9 CVE-2025-31100 Unrestricted Upload of File with Dangerous Type vulnerability in Mojoomla School Management allows Upload a Web Shell to a Web Server.This issue affects School… School Management: from n/a 2025-08-31 medium6.5 CVE-2025-48108 Missing Authorization vulnerability in Mojoomla School Management allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sc… School Management: from n/a 2025-08-26 high8.5 CVE-2025-54301 A stored XSS vulnerability in Quantum Manager component 1.0.0-3.2.0 for Joomla was discovered. 2025-08-25 high8.5 CVE-2025-54300 A stored XSS vulnerability in Quantum Manager component 1.0.0-3.2.0 for Joomla was discovered. 2025-08-25 high8.7 CVE-2025-54475 A SQL injection vulnerability in the JS Jobs plugin versions 1.3.2-1.4.4 for Joomla allows low-privilege users to execute arbitrary SQL commands. 2025-08-15 high8.5 CVE-2025-54474 A SQLi vulnerability in DJ-Classifieds component 3.9.2-3.10.1 for Joomla was discovered. 2025-08-15 critical9.2 CVE-2025-54473 An authenticated RCE vulnerability in Phoca Commander component 1.0.0-4.0.0 and 5.0.0-5.0.1 for Joomla was discovered. 2025-08-15 critical9.4 CVE-2025-54299 A stored XSS vulnerability in No Boss Testimonials component 1.0.0-3.0.0 and 4.0.0-4.0.2 for Joomla was discovered. 2025-07-28 critical9.4 CVE-2025-54298 A stored XSS vulnerability in CommentBox component 1.0.0-1.1.0 for Joomla was discovered. 2025-07-28 high7.0 CVE-2025-54297 A stored XSS vulnerability in CComment component 5.0.0-6.1.14 for Joomla was discovered. 2025-07-23 high7.0 CVE-2025-54296 A stored XSS vulnerability in ProFiles component 1.0-1.5.0 for Joomla was discovered. 2025-07-23 medium5.1 CVE-2025-54295 A Reflected XSS vulnerability in DJ-Reviews component 1.0-1.3.6 for Joomla was discovered. 2025-07-23 critical9.3 CVE-2025-54294 A SQLi vulnerability in Komento component 4.0.0-4.0.7for Joomla was discovered. 2025-07-23 high8.5 CVE-2025-50127 A SQLi vulnerability in DJ-Flyer component 1.0-3.2 for Joomla was discovered. 2025-07-23

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.