NetSight

Security Dashboard

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

Reset
254 matching advisories · page 1 of 9Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.1 CVE-2026-126754 cPanel & WHM 11.134.0.13 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the mpidentity… cPanel, L.L.C. · cPanel & WHM 3 days ago medium6.5 CVE-2026-110686 Cpanel::JSON::XS versions before 4.80 for Perl use freed filter callbacks when a filter removes itself during decoding in decode_hv. Cpanel::JSON::XS 33 days ago medium6.5 CVE-2026-110674 Cpanel::JSON::XS versions from 4.33 before 4.80 for Perl miss duplicate non-ASCII bare keys, allowing type confusion under dupkeys_as_arrayref in decode_hv. Cpanel::JSON::XS versions from 33 days ago medium5.6 CVE-2026-58047 HTTP Smuggling in cPanel allows potential leak of credentials. 2026-07-31 medium5.6 CVE-2025-40929 Cpanel::JSON::XS before version 4.40 for Perl has an integer buffer overflow causing a segfault when parsing crafted JSON, enabling denial-of-service attacks o… 2025-09-08 medium5.3 CVE-2025-43921 GNU Mailman 2.1.39, as bundled in cPanel (and WHM), allows unauthenticated attackers to create lists via the /mailman/create endpoint. gnu · mailman 2025-04-20 medium5.4 CVE-2025-43920 GNU Mailman 2.1.39, as bundled in cPanel (and WHM), in certain external archiver configurations, allows unauthenticated attackers to execute arbitrary OS comma… gnu · mailman 2025-04-20 medium5.8 CVE-2025-43919 GNU Mailman 2.1.39, as bundled in cPanel (and WHM), allows unauthenticated attackers to read arbitrary files via ../ directory traversal at /mailman/private/ma… gnu · mailman 2025-04-20 medium5.3 CVE-2023-29489 An issue was discovered in cPanel before 11.109.9999.116. cpanel · cpanel 2023-04-27 medium5.5 CVE-2021-38590 In cPanel before 96.0.8, weak permissions on web stats can lead to information disclosure (SEC-584). cpanel · cpanel 2021-08-11 medium4.4 CVE-2021-38586 In cPanel before 98.0.1, /scripts/cpan_config performs unsafe operations on files (SEC-589). cpanel · cpanel 2021-08-11 medium6.1 CVE-2021-31803 cPanel before 94.0.3 allows self-XSS via EasyApache 4 Save Profile (SEC-581). cpanel · cpanel 2021-04-26 medium6.1 CVE-2020-29137 cPanel before 90.0.17 allows self-XSS via the WHM Transfer Tool interface (SEC-577). cpanel · cpanel 2020-11-27 medium6.5 CVE-2020-29136 In cPanel before 90.0.17, 2FA can be bypassed via a brute-force approach (SEC-575). cpanel · cpanel 2020-11-27 medium4.1 CVE-2020-29135 cPanel before 90.0.17 has multiple instances of URL parameter injection (SEC-567). cpanel · cpanel 2020-11-27 medium6.1 CVE-2020-26115 cPanel before 90.0.10 allows self XSS via the Cron Editor interface (SEC-574). cpanel · cpanel 2020-09-25 medium6.1 CVE-2020-26114 cPanel before 90.0.10 allows self XSS via the Cron Jobs interface (SEC-573). cpanel · cpanel 2020-09-25 medium6.1 CVE-2020-26113 cPanel before 90.0.10 allows self XSS via WHM Manage API Tokens interfaces (SEC-569). cpanel · cpanel 2020-09-25 medium6.1 CVE-2020-26111 cPanel before 90.0.10 allows self XSS via the WHM Edit DNS Zone interface (SEC-566). cpanel · cpanel 2020-09-25 medium6.1 CVE-2020-26110 cPanel before 88.0.13 allows self XSS via DNS Zone Manager DNSSEC interfaces (SEC-564). cpanel · cpanel 2020-09-25 medium5.3 CVE-2020-12784 cPanel before 86.0.14 allows remote attackers to trigger a bandwidth suspension via mail log strings (SEC-505). cpanel · cpanel 2020-05-11 medium6.5 CVE-2020-10122 cPanel before 84.0.20 allows a webmail or demo account to delete arbitrary files (SEC-547). cpanel · cpanel 2020-03-17 medium5.3 CVE-2020-10116 cPanel before 84.0.20 allows attackers to bypass intended restrictions on features and demo accounts via WebDisk UAPI calls (SEC-541). cpanel · cpanel 2020-03-17 medium6.1 CVE-2020-10114 cPanel before 84.0.20 allows stored self-XSS via the HTML file editor (SEC-535). cpanel · cpanel 2020-03-17 medium6.1 CVE-2020-10113 cPanel before 84.0.20 allows self XSS via a temporary character-set specification (SEC-515). cpanel · cpanel 2020-03-17 medium5.4 CVE-2019-20497 cPanel before 82.0.18 allows stored XSS via WHM Backup Restoration (SEC-533). cpanel · cpanel 2020-03-17 medium5.5 CVE-2019-20496 cPanel before 82.0.18 allows attackers to conduct arbitrary chown operations as root during log processing (SEC-532). cpanel · cpanel 2020-03-17 medium6.5 CVE-2019-20495 cPanel before 82.0.18 allows attackers to read an arbitrary database via MySQL dump streaming (SEC-531). cpanel · cpanel 2020-03-17 medium6.1 CVE-2019-20493 cPanel before 82.0.18 allows self-XSS because JSON string escaping is mishandled (SEC-520). cpanel · cpanel 2020-03-17 medium5.4 CVE-2019-20491 cPanel before 82.0.18 allows attackers to leverage virtual mail accounts in order to bypass account suspensions (SEC-508). cpanel · cpanel 2020-03-16

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.