NetSight

Security Dashboard

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

Reset
11,246 matching advisories · page 2 of 375Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.9 CVE-2026-130348 phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authorization vulnerability that exposes restricted and inactive category met… thorsten · phpMyFAQ 5 days ago medium5.3 CVE-2026-130349 phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability that allows category- or language-restricted editors to bypass … thorsten · phpMyFAQ 5 days ago medium5.1 CVE-2026-130350 phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an incorrect authorization vulnerability that allows delegated group or user admins to remove… thorsten · phpMyFAQ 5 days ago medium6.9 CVE-2026-130352 phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows unauthenticated attackers to read editor-… thorsten · phpMyFAQ 5 days ago medium6.9 CVE-2026-130353 phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability in its public FAQ REST API that exposes author names … thorsten · phpMyFAQ 5 days ago medium6.9 CVE-2026-130354 phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass vulnerability in POST /api/webauthn/prepare that creates accou… thorsten · phpMyFAQ 5 days ago medium5.3 CVE-2026-130355 phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability in POST /admin/api/faq/import that lets FAQ_ADD users bypass th… thorsten · phpMyFAQ 5 days ago medium5.3 CVE-2026-130356 phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass that lets category- or language-restricted editors rewrite visibility ACLs and t… thorsten · phpMyFAQ 5 days ago medium5.1 CVE-2026-130363 phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability that lets scoped editors view out-of-scope draft FAQs because t… thorsten · phpMyFAQ 5 days ago medium6.9 CVE-2026-130362 phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an account enumeration vulnerability that allows unauthenticated attackers to identify … thorsten · phpMyFAQ 5 days ago medium4.4 CVE-2026-130365 phpMyFAQ from 4.2.0-alpha before 4.2.0-RC.2 contains a stored cross-site scripting vulnerability that allows FAQ_EDIT users to bypass SvgSanitizer using namesp… thorsten · phpMyFAQ 5 days ago medium5.3 CVE-2026-130367 phpMyFAQ through 4.1.12 and from 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the admin FAQ copy and translate pages, which … thorsten · phpMyFAQ 5 days ago medium4.2 CVE-2026-130368 phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an improper restriction of excessive authentication attempts vulnerability in PasswordC… thorsten · phpMyFAQ 5 days ago medium4.2 CVE-2026-130370 phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authentication vulnerability that allows attackers holding a hijacked session… thorsten · phpMyFAQ 5 days ago medium5.1 CVE-2026-130377 phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability in DELETE /admin/api/faq/delete that lets language-scoped FAQ_D… thorsten · phpMyFAQ 5 days ago medium5.3 CVE-2026-130381 phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass vulnerability that allows language-scoped editors to read other translations by … thorsten · phpMyFAQ 5 days ago medium5.1 CVE-2026-130383 phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass vulnerability that allows authenticated editors to manipulate searc… thorsten · phpMyFAQ 5 days ago medium4.4 CVE-2026-91114 Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. silverstripe · silverstripe-framework 5 days ago medium6.4 CVE-2026-91110 Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. silverstripe · silverstripe-framework 5 days ago medium4.3 CVE-2026-88989 Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. composer · silverstripe/framework 5 days ago medium6.8 CVE-2026-91112 Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. composer · silverstripe/framework 5 days ago medium5.3 CVE-2026-129248 Akaunting Invoice Item Validation helpers.php calculation_to_quantity numeric range comparison without minimum check n/a · Akaunting 7 days ago medium5.3 CVE-2026-63173 Omnispace Agora Project through 26.10.0 contains a broken access control vulnerability in which the isAutor() function in MdlObject.php grants accessRight=3 ba… Omnispace · Agora Project 8 days ago medium4.2 CVE-2026-129132 MRBS before 1.13.0 contains an LDAP injection vulnerability in web/lib/MRBS/Auth/AuthLdap.php that interpolates unescaped login usernames into DN search and gr… meeting-room-booking-system · mrbs-code 8 days ago medium6.5 CVE-2026-125835 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Crocoblock JetTabs jet-tabs allows Stored XSS.This issue … Crocoblock · JetTabs 8 days ago medium5.3 CVE-2026-126374 Vvveb through 1.0.8.6 contains an SQL injection vulnerability because the @KEYS(:each) macro emits PHP array keys as backtick-quoted INSERT column names withou… givanz · Vvveb 8 days ago medium5.3 CVE-2026-126417 OpenEMR before 8.5.0 contains an access control flaw in get_claim_file.php: with location=tmp, it serves any file in the shared temporary directory without ver… openemr · openemr, Open-Emr · OpenEMR, open-emr · openemr 8 days ago medium6.3 CVE-2026-126418 OpenEMR before 8.5.0 contains a stored cross-site scripting vulnerability in interface/billing/sl_eob_invoice.php, which escapes billing codes for HTML attribu… openemr · openemr, Open-Emr · OpenEMR, open-emr · openemr 8 days ago medium5.4 CVE-2026-126419 OpenEMR before 8.5.0 contains a missing authorization vulnerability in the esign_form_submit handler of library/ESign/Form/Controller.php that verifies only th… openemr · openemr, Open-Emr · OpenEMR, open-emr · openemr 8 days ago medium5.9 CVE-2026-126420 OpenEMR before 8.5.0 contains a missing authorization vulnerability in the FaxSMS module's utility.php that allows read-only demographics users to create patie… openemr · openemr, Open-Emr · OpenEMR, open-emr · openemr 8 days ago

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.