NetSight

Security Dashboard

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

Reset
128 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2021-33508 Cross-site scripting in Plone pip · Plone 2021-05-21 medium6.1 CVE-2021-33507 Cross-site scripting in Products.CMFCore, Products.PluggableAuthService, Plone pip · Products.CMFCore, pip · Products.PluggableAuthService, pip · Plone 2021-05-21 high6.8 CVE-2021-32633 Remote Code Execution via traversal in TAL expressions pip · Zope 2021-05-21 medium6.1 CVE-2021-3313 Plone XSS in User Fullname Property and File Upload pip · plone 2021-05-20 medium5.4 CVE-2021-29002 Plone XSS Vulnerability pip · plone 2021-03-24 high6.5 CVE-2021-21336 Exposure of Sensitive Information to an Unauthorized Actor in Products.PluggableAuthService ZODBRoleManager pip · Products.PluggableAuthService 2021-03-08 high8.8 CVE-2020-28736 Improper Restriction of XML External Entity Reference in Plone pip · Plone, pip · plone.app.event, pip · plone.app.theming +2 2020-12-30 high8.8 CVE-2020-28735 SSRF attacks via tracebacks in Plone pip · Plone, pip · plone.app.event, pip · plone.app.theming +2 2020-12-30 high8.8 CVE-2020-28734 Improper Restriction of XML External Entity Reference in Plone pip · Plone, pip · plone.app.event, pip · plone.app.theming +2 2020-12-30 critical9.8 CVE-2020-35190 The official plone Docker images before version of 4.3.18-alpine (Alpine specific) contain a blank password for a root user. plone · plone 2020-12-17 critical9.8 CVE-2020-7941 Plone Unauthenticated Write Vulnerability pip · Plone, pip · plone.app.contenttypes 2020-01-23 high7.5 CVE-2020-7940 Plone allows weak passwords pip · Plone 2020-01-23 high8.8 CVE-2020-7939 Plone SQL Injection Vulnerability pip · Plone 2020-01-23 high8.8 CVE-2020-7938 Plone Privilege Escallation pip · plone.restapi, pip · Plone 2020-01-23 medium5.4 CVE-2020-7937 Plone cross site scripting (XSS) pip · Plone 2020-01-23 medium6.1 CVE-2020-7936 Plone Open Redirect Vulnerability pip · Plone 2020-01-23 medium6.1 CVE-2013-7062 Plone Zope cross-site scripting (XSS) vulnerability pip · plone 2020-01-02 medium6.1 CVE-2017-1000484 Plone Open Redirect pip · plone, pip · Plone 2018-01-03 high6.5 CVE-2017-1000483 Plone Unauthorized Access Vulnerability pip · Plone 2018-01-03 medium5.4 CVE-2017-1000482 Products.CMFPlone XSS in profile home_page property pip · Products.CMFPlone, pip · Plone 2018-01-03 medium6.1 CVE-2017-1000481 Products.CMFPlone Open Redirect Vulnerability pip · Products.CMFPlone, pip · Plone 2018-01-03 high8.8 CVE-2015-7293 Plone vulnerable to cross-site request forgery pip · Plone 2017-09-25 high7.5 CVE-2015-7318 Plone Header Injection pip · Plone 2017-09-25 medium6.8 CVE-2015-7317 Kupu 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, and 4.2.0 through 4.2.7 allows remote authenticated users to edit Kupu settings. kupu_project · kupu, plone · plone 2017-09-25 medium6.1 CVE-2015-7316 Plone Cross-site Scripting Vulnerability pip · plone, pip · Plone 2017-09-25 high5.9 CVE-2015-7315 Plone unauthorized member addition vulnerability pip · Products.CMFPlone, pip · Plone 2017-09-25 medium4.3 CVE-2017-5524 Plone Sandbox Escape pip · Plone 2017-03-23 medium6.1 CVE-2016-7140 Plone vulnerable to Cross-site Scripting pip · Plone 2017-03-07 medium6.1 CVE-2016-7139 Plone Cross-site Scripting (XSS) vulnerability pip · Plone 2017-03-07 medium6.1 CVE-2016-7138 Plone XSS pip · plone 2017-03-07

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.