NetSight

Security Dashboard

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

Reset
63 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2024-31503 Dolibarr vulnerable to Cross-Site Request Forgery composer · dolibarr/dolibarr 2024-04-17 high8.8 CVE-2024-29477 Dolibarr ERP CRM Code Injection vulnerability during installation composer · dolibarr/dolibarr 2024-04-03 high7.1 CVE-2024-23817 Dolibarr Application Home Page has HTML injection vulnerability composer · dolibarr/dolibarr 2024-01-25 high7.5 CVE-2023-4197 Dolibarr Improper Input Validation vulnerability composer · dolibarr/dolibarr 2023-11-01 high8.8 CVE-2023-38887 File Upload vulnerability in Dolibarr ERP CRM composer · dolibarr/dolibarr 2023-09-20 high7.2 CVE-2023-38886 Dolibarr allows a remote privileged attacker to execute arbitrary code via a crafted command/script composer · dolibarr/dolibarr 2023-09-20 high7.5 CVE-2023-33568 Dolibarr vulnerable to unauthenticated database access composer · dolibarr/dolibarr 2023-06-13 high8.8 CVE-2023-30253 Dolibarr vulnerable to remote code execution via uppercase manipulation composer · dolibarr/dolibarr 2023-05-29 high7.5 CVE-2021-37517 Access Control vulnerability in Dolibarr composer · dolibarr/dolibarr 2022-03-31 high8.8 CVE-2021-36625 SQL Injection in Dolibarr composer · dolibarr/dolibarr 2022-03-31 high8.8 CVE-2022-0819 Code injection in dolibarr/dolibarr composer · dolibarr/dolibarr 2022-03-02 high8.8 CVE-2021-25957 Weak Password Recovery Mechanism for Forgotten Password composer · dolibarr/dolibarr 2021-08-17 high7.2 CVE-2021-25956 Dolibarr vulnerable to Improper Authentication and Improper Access Control composer · dolibarr/dolibarr 2021-08-17 high7.2 CVE-2020-35136 Dolibarr authenticated Remote Code Execution composer · dolibarr/dolibarr 2020-12-23 high8.8 CVE-2020-14209 Dolibarr Unrestricted Upload of File with Dangerous Type composer · dolibarr/dolibarr 2020-09-02 high8.8 CVE-2020-14443 Dolibarr SQL injection vulnerability in accountancy/customer/card.php composer · dolibarr/dolibarr 2020-06-18 high8.8 CVE-2020-12669 Incorrect Authorization in Dolibarr composer · dolibarr/dolibarr 2020-05-06 high8.8 CVE-2020-11825 Dolibarr Cross-Site Request Forgery Vulnerability composer · dolibarr/dolibarr 2020-04-16 high7.5 CVE-2019-19209 Dolibarr ERP and CRM SQLi composer · dolibarr/dolibarr 2020-03-16 high8.0 CVE-2019-15062 Dolibarr Cross-Site Request Forgery (CSRF) composer · dolibarr/dolibarr 2019-08-14 high8.0 CVE-2019-11201 Dolibarr ERP and CRM Code Injection composer · dolibarr/dolibarr 2019-07-29 high8.8 CVE-2019-11200 Dolibarr ERP and CRM malicious executable loading composer · dolibarr/dolibarr 2019-07-29 high8.8 CVE-2019-1010054 Dolibarr Cross Site Request Forgery (CSRF) composer · dolibarr/dolibarr 2019-07-18 high8.8 CVE-2018-19998 Dolibarr SQL injection vulnerability in user/card.php composer · dolibarr/dolibarr 2019-01-03 high8.8 CVE-2018-19994 Dolibarr error-based SQL injection vulnerability in product/card.php composer · dolibarr/dolibarr 2019-01-03 high8.0 CVE-2018-10092 Dolibarr arbitrary commands execution composer · dolibarr/dolibarr 2018-05-22 high8.8 CVE-2017-9839 Dolibarr SQL injection via type parameter in product/stats/card.php composer · dolibarr/dolibarr 2018-04-11 high8.8 CVE-2017-18260 Dolibarr SQL injection vulnerability composer · dolibarr/dolibarr 2018-04-11 high7.5 CVE-2017-17898 Dolibarr sensitive information disclosure composer · dolibarr/dolibarr 2017-12-27 high7.5 CVE-2017-14240 Dolibarr ERP and CRM Sensitive Data Disclosure composer · dolibarr/dolibarr 2017-09-11

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.