NetSight

Security Dashboard

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

Reset
60 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
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 high7.2 CVE-2023-1211 SQL Injection 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 low2.4 CVE-2022-3845 A vulnerability has been found in phpipam and classified as problematic. phpipam · phpipam 2022-11-02 critical9.8 CVE-2022-41443 phpipam v1.5.0 was discovered to contain a header injection vulnerability via the component /admin/subnets/ripe-query.php. phpipam · phpipam 2022-10-03 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 high7.2 CVE-2022-23046 PhpIPAM v1.4.4 allows an authenticated admin user to inject SQL sentences in the "subnet" parameter while searching a subnet via app/admin/routing/edit-bgp-map… phpipam · phpipam 2022-01-19 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 high8.8 CVE-2020-7988 An issue was discovered in tools/pass-change/result.php in phpIPAM 1.4. phpipam · phpipam 2020-03-04 critical9.8 CVE-2019-16696 phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/edit.php table parameter when action=add is used. phpipam · phpipam 2019-09-22 critical9.8 CVE-2019-16695 phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/filter.php table parameter when action=add is used. phpipam · phpipam 2019-09-22 critical9.8 CVE-2019-16694 phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/edit-result.php table parameter when action=add is used. phpipam · phpipam 2019-09-22 critical9.8 CVE-2019-16693 phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/order.php table parameter when action=add is used. phpipam · phpipam 2019-09-22 critical9.8 CVE-2019-16692 phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/filter-result.php table parameter when action=add is used. phpipam · phpipam 2019-09-22 medium6.1 CVE-2019-1000010 phpIPAM version 1.3.2 and earlier contains a Cross Site Scripting (XSS) vulnerability in subnet-scan-telnet.php that can result in executing code in victims br… phpipam · phpipam 2019-02-04 medium5.4 CVE-2018-1000870 PHPipam version 1.3.2 and earlier contains a CWE-79 vulnerability in /app/admin/users/print-user.php that can result in Execute code in the victims browser. phpipam · phpipam 2018-12-20 critical9.8 CVE-2018-1000869 phpIPAM version 1.3.2 contains a CWE-89 vulnerability in /app/admin/nat/item-add-submit.php that can result in SQL Injection.. phpipam · phpipam 2018-12-20 medium4.7 CVE-2018-1000860 phpipam version 1.3.2 and earlier contains a Cross Site Scripting (XSS) vulnerability in The value of the phpipamredirect cookie is copied into an HTML tag on … phpipam · phpipam 2018-12-20 medium6.1 CVE-2018-10329 app/tools/mac-lookup/index.php in phpIPAM 1.3.1 has Reflected XSS on /tools/mac-lookup/ via the mac parameter. phpipam · phpipam 2018-04-24 medium5.4 CVE-2017-15640 app/sections/user-menu.php in phpIPAM before 1.3.1 has XSS via the ip parameter. phpipam · phpipam 2018-04-21 medium6.1 CVE-2017-6481 Multiple Cross-Site Scripting (XSS) issues were discovered in phpipam 1.2. phpipam · phpipam 2017-03-05 medium4.3 CVE-2015-6529 Multiple cross-site scripting (XSS) vulnerabilities in phpipam 1.1.010 allow remote attackers to inject arbitrary web script or HTML via the (1) section parame… phpipam · phpipam 2015-08-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.