Vulnerability Database · Packagist · Package report

dcat/laravel-admin: vulnerability history, versions and safety

dcat/laravel-admin is a package in the Packagist ecosystem. Vulert records 4 vulnerabilities for it across 63 releases, from May 2023 to Dec 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M4
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on dcat/laravel-admin i

Updated on 23 Oct 2026

Careful: 4 of the 4 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 4 vulnerabilities on record across 1 year, none in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 28 Dec 2024 i
  • Highest CVSS 6.1 i
  • With no published fix 4 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for dcat/laravel-admin, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.2.0-beta M2 No Details →
2.1.3-beta M2 No Details →
2.1.2-beta M2 No Details →
2.1.1-beta M2 No Details →
2.1.0-beta M2 No Details →
2.0.24-beta M2 No Details →
2.0.23-beta M2 No Details →
2.0.22-beta M2 No Details →
2.0.21-beta M2 No Details →
2.0.20-beta M2 No Details →
2.0.19-beta M2 No Details →
2.0.18-beta M2 No Details →
2.0.17-beta M2 No Details →
2.0.16-beta M2 No Details →
2.0.15-beta M2 No Details →
2.0.14-beta M2 No Details →
2.0.13-beta M2 No Details →
2.0.12-beta M2 No Details →
2.0.11-beta M2 No Details →
2.0.10-beta M2 No Details →
2.0.9-beta M2 No Details →
2.0.8-beta M2 No Details →
2.0.7-beta M2 No Details →
2.0.6-beta M2 No Details →
2.0.5-beta M2 No Details →
2.0.4-beta M2 No Details →
2.0.3-beta M2 No Details →
2.0.2-beta M2 No Details →
2.0.1-beta M2 No Details →
2.0.0-beta M2 No Details →
1.7.9 M2 No Details →
1.7.8 M2 No Details →
1.7.7 M2 No Details →
1.7.6 M2 No Details →
1.7.5 M2 No Details →
1.7.4 M2 No Details →
1.7.3 M2 No Details →
1.7.2 M2 No Details →
1.7.1 M2 No Details →
1.7.0 M2 No Details →
1.6.5 M2 No Details →
1.6.0 M2 No Details →
1.5.3 M2 No Details →
1.5.2 M2 No Details →
1.5.0 M2 No Details →
1.4.8 M2 No Details →
1.4.7 M2 No Details →
1.4.6 M2 No Details →
1.4.5 M2 No Details →
1.4.0 M2 No Details →
1.3.4 M2 No Details →
1.3.2 M2 No Details →
1.3.0 M2 No Details →
1.2.5 M2 No Details →
1.2.0 M2 No Details →
1.1.0 M2 No Details →
1.0.1 M2 No Details →
1.0.0 M2 No Details →
0.9.0 M2 No Details →
0.8.2 M2 No Details →
0.8.1 M2 No Details →
0.8.0 M2 No Details →
0.1.0 M2 No Details →

Newest 63 of 63 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for dcat/laravel-admin

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About dcat/laravel-admin

Is dcat/laravel-admin safe to use?

Vulert records 4 vulnerabilities for dcat/laravel-admin in Packagist: 0 critical, 0 high, 4 medium and 0 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does dcat/laravel-admin have?

4 vulnerabilities are recorded for dcat/laravel-admin in the Packagist ecosystem: 0 critical, 0 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dcat/laravel-admin vulnerabilities disclosed?

0 vulnerabilities were recorded for dcat/laravel-admin in the last 12 months, and the oldest entry in this database dates to 31 May 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of dcat/laravel-admin are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor dcat/laravel-admin for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dcat/laravel-admin version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.