Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

laravel

About This Vendor

laravel is a technology vendor producing software and infrastructure products. As a software provider, laravel's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of laravel's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 28 known vulnerabilities from laravel. This includes 7 critical-severity issues and 14 high-severity issues that represent significant risk. These vulnerabilities affect 10 distinct products across laravel's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2017 through 2026, reflecting sustained security scrutiny over multiple years. Organizations deploying laravel products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.

ID Date Published Last Modified Severity (CVSSv3) Severity (CVSSv2) Exploit Available
CVE-2017-9303 2017-05-29 2026-05-13 6.1 5.8 Likely
CVE-2017-14775 2017-09-28 2026-05-13 5.9 4.3 Likely
CVE-2017-16894 2017-11-20 2026-05-13 7.5 5.0 Likely
CVE-2018-15133 2018-08-09 2025-11-07 8.1 6.8 Likely
CVE-2018-6330 2019-03-28 2024-11-21 8.8 6.5 Likely
CVE-2020-24940 2020-09-04 2024-11-21 7.5 4.3 Likely
CVE-2020-24941 2020-09-04 2024-11-21 7.5 4.3 Likely
CVE-2021-3129 2021-01-12 2025-11-10 9.8 7.5 Likely
CVE-2021-21263 2021-01-19 2024-11-21 7.2 5.0 Likely
CVE-2021-43617 2021-11-14 2024-11-21 9.8 7.5 Likely
CVE-2021-43808 2021-12-08 2024-11-21 5.3 4.3 Likely
CVE-2020-19316 2021-12-20 2024-11-21 8.8 6.8 Likely
CVE-2022-25838 2022-02-24 2024-11-21 8.1 6.8 Likely
CVE-2022-2870 2022-08-17 2024-11-21 4.1 - -
CVE-2022-2886 2022-08-19 2024-11-21 5.0 - -
CVE-2021-28254 2023-04-19 2025-03-05 9.8 - -
CVE-2022-40482 2023-04-25 2025-05-30 5.3 - -
CVE-2024-22859 2024-02-01 2025-05-29 8.8 - -
CVE-2024-21504 2024-03-19 2025-08-25 6.1 - -
CVE-2024-47823 2024-10-08 2025-03-06 9.8 - -
CVE-2024-52301 2024-11-12 2025-08-26 7.5 - -
CVE-2024-55661 2024-12-13 2025-08-25 8.8 - -
CVE-2025-27515 2025-03-05 2025-08-26 9.8 - -
CVE-2024-13918 2025-03-10 2025-03-24 8.0 - -
CVE-2024-13919 2025-03-10 2025-03-24 8.0 - -
CVE-2025-54068 2025-07-17 2026-03-20 9.8 - -
CVE-2026-23524 2026-01-21 2026-03-06 9.8 - -
CVE-2026-39976 2026-04-09 2026-06-02 7.1 - -

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for laravel by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with laravel's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.