NetSight

Security Dashboard

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

Reset
37 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2026-115982 A vulnerability was detected in phpIPAM up to 1.8.3. phpIPAM 28 days ago medium4.3 CVE-2026-108720 phpIPAM through 1.8.3 contains a missing authorization vulnerability that allows authenticated low-privilege users to view restricted subnets and addresses bec… phpIPAM 41 days ago medium4.7 CVE-2026-4189 A weakness has been identified in phpipam up to 1.7.4. phpipam 2026-03-16 medium6.1 CVE-2025-61078 Cross-site scripting (XSS) vulnerability in Request IP form in phpIPAM v1.7.3 allows remote attackers to inject arbitrary web script or HTML via the instructio… phpipam · phpipam 2025-12-09 medium5.4 CVE-2024-55093 phpIPAM through 1.7.3 has a reflected Cross-Site Scripting (XSS) vulnerability in the install scripts. phpipam · phpipam 2025-03-31 medium6.1 CVE-2024-10727 A reflected cross-site scripting (XSS) vulnerability exists in phpipam/phpipam versions 1.5.0 through 1.6.0. phpipam · phpipam 2025-03-20 medium5.4 CVE-2024-10725 A stored cross-site scripting (XSS) vulnerability exists in phpipam/phpipam version 1.5.2. phpipam · phpipam 2025-03-20 medium5.4 CVE-2024-10724 A stored cross-site scripting (XSS) vulnerability exists in phpipam/phpipam version 1.5.2, specifically in the Subnet NAT translations section when editing the… phpipam · phpipam 2025-03-20 medium5.4 CVE-2024-10723 A stored cross-site scripting (XSS) vulnerability was discovered in phpipam/phpipam version 1.5.2. phpipam · phpipam 2025-03-20 medium5.4 CVE-2024-10722 A stored cross-site scripting (XSS) vulnerability exists in phpipam/phpipam version 1.5.2. phpipam · phpipam 2025-03-20 medium5.4 CVE-2024-10721 A stored cross-site scripting (XSS) vulnerability was discovered in phpipam/phpipam version 1.5.2. phpipam · phpipam 2025-03-20 medium6.1 CVE-2024-10720 A stored cross-site scripting (XSS) vulnerability exists in phpipam/phpipam version 1.5.2. phpipam · phpipam 2025-03-20 medium5.4 CVE-2024-10719 A stored cross-site scripting (XSS) vulnerability exists in phpipam version 1.5.2, specifically in the circuits options functionality. phpipam · phpipam 2025-03-20 medium5.9 CVE-2024-0787 phpIPAM version 1.5.1 contains a vulnerability where an attacker can bypass the IP block mechanism to brute force passwords for users by using the 'X-Forwarded… phpipam · phpipam 2024-11-15 medium4.8 CVE-2022-1226 A Cross-Site Scripting (XSS) vulnerability in phpipam/phpipam versions prior to 1.4.7 allows attackers to execute arbitrary JavaScript code in the browser of a… phpipam · phpipam 2024-11-15 medium6.1 CVE-2024-41358 phpipam 1.6 is vulnerable to Cross Site Scripting (XSS) via app\admin\import-export\import-load-data.php. phpipam · phpipam 2024-08-29 medium4.7 CVE-2024-41356 phpipam 1.6 is vulnerable to Cross Site Scripting (XSS) via app\admin\firewall-zones\zones-edit-network.php. phpipam · phpipam 2024-07-26 medium6.5 CVE-2024-41355 phpipam 1.6 is vulnerable to Cross Site Scripting (XSS) via /app/tools/request-ip/index.php. phpipam · phpipam 2024-07-26 medium6.1 CVE-2023-24657 phpipam v1.6 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the closeClass parameter at /subnet-masks/popup.php. phpipam · phpipam 2023-03-08 medium4.8 CVE-2023-1212 Cross-site Scripting (XSS) - Stored in GitHub repository phpipam/phpipam prior to v1.5.2. phpipam · phpipam 2023-03-07 medium5.3 CVE-2023-0678 Missing Authorization in GitHub repository phpipam/phpipam prior to v1.5.1. phpipam · phpipam 2023-02-04 medium6.1 CVE-2023-0677 Cross-site Scripting (XSS) - Reflected in GitHub repository phpipam/phpipam prior to v1.5.1. phpipam · phpipam 2023-02-04 medium6.1 CVE-2023-0676 Cross-site Scripting (XSS) - Reflected in GitHub repository phpipam/phpipam prior to 1.5.1. phpipam · phpipam 2023-02-04 medium6.5 CVE-2022-1225 Incorrect Privilege Assignment in GitHub repository phpipam/phpipam prior to 1.4.6. phpipam · phpipam 2022-04-04 medium6.5 CVE-2022-1224 Improper Authorization in GitHub repository phpipam/phpipam prior to 1.4.6. phpipam · phpipam 2022-04-04 medium6.5 CVE-2022-1223 Incorrect Authorization in GitHub repository phpipam/phpipam prior to 1.4.6. phpipam · phpipam 2022-04-04 medium6.1 CVE-2021-46426 phpIPAM 1.4.4 allows Reflected XSS and CSRF via app/admin/subnets/find_free_section_subnets.php of the subnets functionality. phpipam · phpipam 2022-03-25 medium4.8 CVE-2022-23045 PhpIPAM v1.4.4 allows an authenticated admin user to inject persistent JavaScript code inside the "Site title" parameter while updating the site settings. phpipam · phpipam 2022-01-19 medium6.1 CVE-2021-35438 phpIPAM 1.4.3 allows Reflected XSS via app/dashboard/widgets/ipcalc-result.php and app/tools/ip-calculator/result.php of the IP calculator. phpipam · phpipam 2021-06-23 medium4.8 CVE-2020-13225 phpIPAM 1.4 contains a stored cross site scripting (XSS) vulnerability within the Edit User Instructions field of the User Instructions widget. phpipam · phpipam 2020-05-20

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.