NetSight

Security Dashboard

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

Reset
479 matching advisories · page 13 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2018-20895 In cPanel before 71.9980.37, API tokens retain ACLs after those ACLs are removed from the corresponding accounts (SEC-393). cpanel · cpanel 2019-08-01 low3.3 CVE-2018-20894 cPanel before 74.0.0 makes web-site contents accessible to other local users via Git repositories (SEC-443). cpanel · cpanel 2019-08-01 low2.3 CVE-2018-20893 cPanel before 74.0.0 allows file-rename operations during account renames (SEC-442). cpanel · cpanel 2019-08-01 medium4.3 CVE-2018-20892 cPanel before 74.0.0 allows arbitrary zone file modifications because of incorrect CAA record handling (SEC-439). cpanel · cpanel 2019-08-01 medium5.5 CVE-2018-20891 cPanel before 74.0.0 allows arbitrary file-read operations during File Restoration (SEC-436). cpanel · cpanel 2019-08-01 medium4.3 CVE-2018-20890 cPanel before 74.0.0 allows arbitrary zone file modifications during record edits (SEC-426). cpanel · cpanel 2019-08-01 medium4.4 CVE-2018-20889 cPanel before 74.0.0 allows certain file-read operations via password file caching (SEC-425). cpanel · cpanel 2019-08-01 medium5.5 CVE-2018-20888 cPanel before 74.0.0 allows file modification in the context of the root account because of incorrect HTTP authentication (SEC-424). cpanel · cpanel 2019-08-01 critical9.8 CVE-2018-20887 cPanel before 74.0.0 allows SQL injection during database backups (SEC-420). cpanel · cpanel 2019-08-01 medium5.3 CVE-2018-20886 cPanel before 74.0.0 insecurely stores phpMyAdmin session files (SEC-418). cpanel · cpanel 2019-08-01 medium5.3 CVE-2018-20885 cPanel before 74.0.0 allows Apache HTTP Server configuration injection because of DocumentRoot variable interpolation (SEC-416). cpanel · cpanel 2019-08-01 medium5.4 CVE-2018-20884 cPanel before 74.0.0 allows stored XSS in the WHM File Restoration interface (SEC-367). cpanel · cpanel 2019-08-01 medium6.5 CVE-2018-20883 cPanel before 74.0.8 allows FTP access during account suspension (SEC-449). cpanel · cpanel 2019-08-01 medium6.8 CVE-2018-20882 cPanel before 74.0.8 allows arbitrary file-write operations in the context of the root account during WHM Force Password Change (SEC-447). cpanel · cpanel 2019-08-01 medium5.4 CVE-2018-20881 cPanel before 74.0.8 allows self stored XSS on the Security Questions login page (SEC-446). cpanel · cpanel 2019-08-01 low3.3 CVE-2018-20880 cPanel before 74.0.8 mishandles account suspension because of an invalid email_accounts.json file (SEC-445). cpanel · cpanel 2019-08-01 medium6.3 CVE-2018-20879 cPanel before 74.0.8 allows demo accounts to execute arbitrary code via the Fileman::viewfile API (SEC-444). cpanel · cpanel 2019-08-01 medium5.4 CVE-2018-20878 cPanel before 74.0.8 allows stored XSS in WHM "File and Directory Restoration" interface (SEC-441). cpanel · cpanel 2019-08-01 medium5.4 CVE-2018-20877 cPanel before 74.0.8 allows self XSS in WHM Style Upload interface (SEC-437). cpanel · cpanel 2019-08-01 medium5.4 CVE-2018-20876 cPanel before 74.0.8 allows self XSS in the Site Software Moderation interface (SEC-434). cpanel · cpanel 2019-08-01 medium5.4 CVE-2018-20875 cPanel before 74.0.8 allows self XSS in the WHM Security Questions interface (SEC-433). cpanel · cpanel 2019-08-01 medium5.4 CVE-2018-20874 cPanel before 74.0.8 allows self XSS in the WHM "Create a New Account" interface (SEC-428). cpanel · cpanel 2019-08-01 low3.3 CVE-2018-20873 cPanel before 74.0.8 allows local users to disable the ClamAV daemon (SEC-409). cpanel · cpanel 2019-08-01 low3.3 CVE-2019-14414 In cPanel before 78.0.2, a Userdata cache temporary file can conflict with domains (SEC-478). cpanel · cpanel 2019-07-30 medium4.3 CVE-2019-14413 cPanel before 78.0.2 allows certain file-write operations as shared users during connection resets (SEC-476). cpanel · cpanel 2019-07-30 low3.3 CVE-2019-14412 Maketext in cPanel before 78.0.2 allows format-string injection in the DCV check_domains_via_dns UAPI (SEC-474). cpanel · cpanel 2019-07-30 medium5.3 CVE-2019-14411 cPanel before 78.0.2 does not properly restrict demo accounts from writing to files via the DCV UAPI (SEC-473). cpanel · cpanel 2019-07-30 low3.3 CVE-2019-14410 Maketext in cPanel before 78.0.2 allows format-string injection in the Email store_filter UAPI (SEC-472). cpanel · cpanel 2019-07-30 medium5.5 CVE-2019-14409 cPanel before 78.0.2 allows arbitrary file-read operations via Passenger adminbin (SEC-466). cpanel · cpanel 2019-07-30 medium4.3 CVE-2019-14408 cPanel before 78.0.2 allows a demo account to link with an OpenID provider (SEC-460). cpanel · cpanel 2019-07-30

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.