NetSight

Security Dashboard

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

Reset
254 matching advisories · page 2 of 9Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2012-6449 The clientconf.html and detailbw.html pages in x3 in cPanel & WHM 11.34.0 (build 8) have a XSS vulnerability. cpanel · cpanel, cpanel · whm 2020-02-10 medium6.1 CVE-2012-6448 Cross-site Scripting (XSS) in cPanel WebHost Manager (WHM) 11.34.0 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. cpanel · webhost_manager 2020-01-27 medium6.1 CVE-2019-17380 cPanel before 82.0.15 allows self XSS in the WHM Update Preferences interface (SEC-528). cpanel · cpanel 2019-10-09 medium6.1 CVE-2019-17379 cPanel before 82.0.15 allows self stored XSS in the WHM SSL Storage Manager interface (SEC-527). cpanel · cpanel 2019-10-09 medium6.1 CVE-2019-17378 cPanel before 82.0.15 allows self XSS in the SSL Key Delete interface (SEC-526). cpanel · cpanel 2019-10-09 medium6.1 CVE-2019-17377 cPanel before 82.0.15 allows self XSS in LiveAPI example scripts (SEC-524). cpanel · cpanel 2019-10-09 medium6.1 CVE-2019-17376 cPanel before 82.0.15 allows self XSS in the SSL Certificate Upload interface (SEC-521). cpanel · cpanel 2019-10-09 medium6.5 CVE-2016-10807 cPanel before 57.9999.54 allows certain denial-of-service outcomes via /scripts/killpvhost (SEC-112). cpanel · cpanel 2019-08-07 medium5.4 CVE-2016-10806 cPanel before 57.9999.54 allows self XSS on the Paper Lantern Landing Page (SEC-110). cpanel · cpanel 2019-08-07 medium5.5 CVE-2016-10799 cPanel before 58.0.4 does not set the Pear tmp directory during a PHP installation (SEC-137). cpanel · cpanel 2019-08-07 medium6.8 CVE-2016-10798 cPanel before 58.0.4 allows a file-ownership change (to nobody) via rearrangeacct (SEC-134). cpanel · cpanel 2019-08-07 medium4.3 CVE-2016-10797 cPanel before 58.0.4 allows WHM "Purchase and Install an SSL Certificate" page visitors to list all server domains (SEC-133). cpanel · cpanel 2019-08-06 medium6.1 CVE-2016-10795 cPanel before 59.9999.145 allows stored XSS in the WHM tail_upcp2.cgi interface (SEC-156). cpanel · cpanel 2019-08-06 medium6.5 CVE-2016-10794 cPanel before 59.9999.145 allows arbitrary file-read operations because of a multipart form processing error (SEC-154). cpanel · cpanel 2019-08-06 medium5.3 CVE-2016-10791 cPanel before 60.0.15 does not ensure that system accounts lack a valid password, so that logins are impossible (CPANEL-9559). cpanel · cpanel 2019-08-06 medium6.5 CVE-2016-10786 cPanel before 60.0.25 allows members of the nobody group to read Apache HTTP Server SSL keys (SEC-186). cpanel · cpanel 2019-08-06 medium6.5 CVE-2016-10785 cPanel before 60.0.25 allows attackers to discover file contents during file copy operations (SEC-185). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10784 cPanel before 60.0.25 allows self XSS in the alias upload interface (SEC-184). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10783 cPanel before 60.0.25 allows self stored XSS in SSL_listkeys (SEC-182). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10782 cPanel before 60.0.25 allows self stored XSS in postgres API1 listdbs (SEC-181). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10781 cPanel before 60.0.25 allows self XSS in the UI_confirm API (SEC-180). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10780 cPanel before 60.0.25 allows stored XSS in the ftp_sessions API (SEC-180). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10779 cPanel before 60.0.25 allows stored XSS in api1_listautoresponders (SEC-179). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10778 cPanel before 60.0.25 allows self stored XSS in the listftpstable API (SEC-178). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10777 cPanel before 60.0.25 allows self XSS in WHM Tweak Settings for autodiscover_host (SEC-177). cpanel · cpanel 2019-08-06 medium5.4 CVE-2016-10776 cPanel before 60.0.25 allows stored XSS during the homedir removal phase of WHM Account termination (SEC-174). cpanel · cpanel 2019-08-06 medium6.5 CVE-2017-18482 cPanel before 62.0.4 allows resellers to use the WHM enqueue_transfer_item API for queueing non-rearrange modules (SEC-213). cpanel · cpanel 2019-08-05 medium5.4 CVE-2017-18481 cPanel before 62.0.4 allows stored XSS in the WHM Account Suspension List interface (SEC-211). cpanel · cpanel 2019-08-05 medium6.5 CVE-2017-18480 cPanel before 62.0.4 does not enforce account ownership for has_mycnf_for_cpuser WHM API calls (SEC-210). cpanel · cpanel 2019-08-05 medium6.5 CVE-2017-18479 In cPanel before 62.0.4, WHM SSL certificate generation uses an unreserved e-mail address (SEC-209). cpanel · cpanel 2019-08-05

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.