NetSight

Security Dashboard

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

Reset
613 matching advisories · page 9 of 21Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2023-3538 A vulnerability classified as problematic was found in SimplePHPscripts Photo Gallery PHP 2.0. simplephpscripts · photo_gallery_php 2023-07-07 low3.5 CVE-2023-3537 A vulnerability classified as problematic has been found in SimplePHPscripts News Script PHP Pro 2.4. simplephpscripts · news_script_php_pro 2023-07-07 low3.5 CVE-2023-3536 A vulnerability was found in SimplePHPscripts Funeral Script PHP 3.1. simplephpscripts · funeral_script_php 2023-07-07 low3.5 CVE-2023-3535 A vulnerability was found in SimplePHPscripts FAQ Script PHP 2.3. simplephpscripts · faq_script_php 2023-07-07 low3.5 CVE-2023-3476 A vulnerability was found in SimplePHPscripts GuestBook Script 2.2. simplephpscripts · guestbook_script 2023-06-30 low3.5 CVE-2023-3475 A vulnerability was found in SimplePHPscripts Event Script 2.1 and classified as problematic. simplephpscripts · event_script 2023-06-30 low3.5 CVE-2023-3474 A vulnerability has been found in SimplePHPscripts Simple Blog 3.2 and classified as problematic. simplephpscripts · simple_blog 2023-06-30 low3.5 CVE-2023-3465 A vulnerability was found in SimplePHPscripts Classified Ads Script 1.8. simplephpscripts · classified_ads_script_php 2023-06-29 low3.5 CVE-2023-3464 A vulnerability was found in SimplePHPscripts Classified Ads Script 1.8. simplephpscripts · classified_ads_script_php 2023-06-29 low3.5 CVE-2023-1948 A vulnerability, which was classified as problematic, has been found in PHPGurukul BP Monitoring Management System 1.0. phpgurukul · bp_monitoring_management_system 2023-04-08 low3.5 CVE-2014-125094 A vulnerability classified as problematic was found in phpMiniAdmin up to 1.8.120510. phpminiadmin_project · phpminiadmin 2023-04-06 low3.3 CVE-2022-48435 In JetBrains PhpStorm before 2023.1 source code could be logged in the local idea.log file jetbrains · phpstorm 2023-04-04 low3.5 CVE-2023-0840 A vulnerability classified as problematic was found in PHPCrazy 1.1.1. phpcrazy_project · phpcrazy 2023-02-15 low3.7 CVE-2023-0641 A vulnerability was found in PHPGurukul Employee Leaves Management System 1.0. employee_leaves_management_system_project · employee_leaves_management_system 2023-02-02 low3.5 CVE-2023-0563 A vulnerability classified as problematic has been found in PHPGurukul Bank Locker Management System 1.0. phpgurukul · bank_locker_management_system 2023-01-28 low3.5 CVE-2023-0527 A vulnerability was found in PHPGurukul Online Security Guards Hiring System 1.0 and classified as problematic. online_security_guards_hiring_system_project · online_security_guards_hiring_system 2023-01-27 low3.5 CVE-2009-10001 A vulnerability classified as problematic was found in jianlinwei cool-php-captcha up to 0.2. cool-php-captcha_project · cool-php-captcha 2023-01-13 low3.5 CVE-2012-10005 A vulnerability has been found in manikandan170890 php-form-builder-class and classified as problematic. php-form-builder-class_project · php-form-builder-class 2023-01-12 low3.5 CVE-2021-4302 A vulnerability was found in slackero phpwcms up to 1.9.26. phpwcms · phpwcms 2023-01-04 low3.5 CVE-2022-4455 A vulnerability was identified in sproctor php-calendar up to 2.0.13. php-calendar · php-calendar 2022-12-13 low2.4 CVE-2022-3845 A vulnerability has been found in phpipam and classified as problematic. phpipam · phpipam 2022-11-02 low2.3 CVE-2022-31628 In PHP versions before 7.4.31, 8.0.24 and 8.1.11, the phar uncompressor code would recursively uncompress "quines" gzip files, resulting in an infinite loop. php · php, fedoraproject · fedora, debian · debian_linux 2022-09-28 low3.5 CVE-2017-20036 A vulnerability, which was classified as problematic, was found in PHPList 3.2.6. phplist · phplist 2022-06-10 low3.5 CVE-2017-20035 A vulnerability, which was classified as problematic, has been found in PHPList 3.2.6. phplist · phplist 2022-06-10 low3.5 CVE-2017-20034 A vulnerability classified as problematic was found in PHPList 3.2.6. phplist · phplist 2022-06-10 low2.7 CVE-2017-20031 A vulnerability was found in PHPList 3.2.6. phplist · phplist 2022-06-10 low3.5 CVE-2021-4232 A vulnerability classified as problematic has been found in Zoo Management System 1.0. phpgurukul · zoo_management_system 2022-05-26 low3.5 CVE-2022-1816 A vulnerability, which was classified as problematic, has been found in Zoo Management System 1.0. phpgurukul · zoo_management_system 2022-05-23 low3.5 CVE-2022-1086 A vulnerability was found in DolphinPHP up to 1.5.0 and classified as problematic. dolphinphp_project · dolphinphp 2022-03-29 low3.5 CVE-2022-1085 A vulnerability was found in CLTPHP up to 6.0. cltphp · cltphp 2022-03-29

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.