NetSight

Security Dashboard

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

Reset
70 matching advisories · page 2 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2019-7356 Subrion CMS v4.2.1 allows XSS via the panel/phrases/ VALUE parameter. intelliants · subrion 2020-11-04 high8.1 CVE-2019-20390 Subrion CMS Cross-Site Request Forgery (CSRF) vulnerability composer · intelliants/subrion 2020-05-15 medium6.1 CVE-2019-20389 Subrion CMS XSS composer · intelliants/subrion 2020-05-15 medium6.5 CVE-2020-12469 Subrion CMS PHP Object Injection composer · intelliants/subrion 2020-04-29 high7.8 CVE-2020-12468 Subrion CMS CSV injection via Export Language composer · intelliants/subrion 2020-04-29 medium6.5 CVE-2020-12467 Session Fixation in Subrion CMS composer · intelliants/subrion 2020-04-29 high8.8 CVE-2018-21037 Subrion CMS CSRF Vulnerability composer · intelliants/subrion 2020-03-17 medium5.4 CVE-2019-17225 Subrion 4.2.1 allows XSS via the panel/members/ Username, Full Name, or Email field, aka an "Admin Member JSON Update" issue. intelliants · subrion 2019-10-06 medium6.1 CVE-2018-11317 Subrion CMS XSS composer · intelliants/subrion 2019-07-03 medium6.1 CVE-2019-11406 Subrion CMS 4.2.1 allows _core/en/contacts/ XSS via the name, email, or phone parameter. intelliants · subrion_cms 2019-05-08 high8.8 CVE-2017-18366 Subrion CMS vulnerable to CSRF in blog/delete composer · intelliants/subrion 2019-04-15 medium5.4 CVE-2018-16631 Subrion CMS v4.2.1 allows XSS via the panel/configuration/general/ SITE TITLE parameter. intelliants · subrion_cms 2018-12-04 medium4.8 CVE-2018-16629 Subrion CMS XSS composer · intelliants/subrion 2018-12-04 high7.2 CVE-2018-19422 Subrion CMS RCE Vulnerability composer · intelliants/subrion 2018-11-21 medium6.1 CVE-2018-15563 Subrion CMS Stored Cross-site Scripting (XSS) composer · intelliants/subrion 2018-10-02 medium4.8 CVE-2018-16327 Subrion Cross-site Scripting (XSS) composer · intelliants/subrion 2018-09-01 medium6.1 CVE-2018-14840 Subrion CMS Cross-site Scripting composer · intelliants/subrion 2018-08-02 medium5.4 CVE-2018-14835 Subrion CMS XSS composer · intelliants/subrion 2018-08-02 high8.8 CVE-2017-15063 Subrion CMS CSRF Vulnerability composer · intelliants/subrion 2017-10-06 critical9.8 CVE-2017-11445 Subrion CMS before 4.1.6 has a SQL injection vulnerability in /front/actions.php via the $_POST array. intelliants · subrion_cms 2017-07-19 critical9.8 CVE-2017-11444 Subrion CMS before 4.1.5.10 has a SQL injection vulnerability in /front/search.php via the $_GET array. intelliants · subrion_cms 2017-07-19 medium6.1 CVE-2017-10795 Subrion Cross-site scripting (XSS) vulnerability composer · intelliants/subrion 2017-07-02 high8.8 CVE-2017-6069 Subrion CMS 4.0.5 has CSRF in admin/blog/add/. intelliants · subrion_cms 2017-03-27 high8.8 CVE-2017-6068 Subrion CMS vulnerable to CSRF in admin/blocks/add composer · intelliants/subrion 2017-03-27 high8.8 CVE-2017-6066 Subrion CMS 4.0.5 has CSRF in admin/languages/edit/1/. intelliants · subrion_cms 2017-03-27 critical9.8 CVE-2017-6013 Subrion CMS 4.0.5.10 has SQL injection in admin/database/ via the query parameter. intelliants · subrion_cms 2017-03-27 high8.8 CVE-2017-6002 Subrion CMS 4.0.5.10 has CSRF in admin/blog/add/. intelliants · subrion_cms 2017-03-27 critical9.8 CVE-2017-5543 Subrion CMS PHP Object Injection composer · intelliants/subrion 2017-01-20 medium6.5 CVE-2015-4129 SQL injection vulnerability in Subrion CMS before 3.3.3 allows remote authenticated users to execute arbitrary SQL commands via modified serialized data in a s… intelliants · subrion_cms 2015-07-05 medium4.3 CVE-2014-9120 Subrion CMS Cross-site scripting in search composer · intelliants/subrion 2014-12-10

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.