Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8

Dcat-Admin Cross-Site Scripting (XSS) vulnerability

CVE-2024-54775GHSA-37x3-j9jq-vrjx

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist dcat/laravel-admin

    Affected
    >= 2.2.0-beta, <= 2.2.0-beta>= 2.2.2-beta, <= 2.2.2-beta
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2024-54775: 0.27% estimated exploitation activity in the next 30 days; percentile 19.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Dcat-Admin v2.2.0-beta and v2.2.2-beta contains a Cross-Site Scripting (XSS) vulnerability via /admin/auth/menu and /admin/auth/extensions.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-37x3-j9jq-vrjx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-54775

Advisory: Dcat-Admin Cross-Site Scripting (XSS) vulnerability
IDs: CVE-2024-54775, GHSA-37x3-j9jq-vrjx
Record: https://patchnext.com/advisories/cve-2024-54775 (revision 1, source checked 26 Oct 2026, 14:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist dcat/laravel-admin: affected >= 2.2.0-beta, <= 2.2.0-beta; >= 2.2.2-beta, <= 2.2.2-beta

## Suggested inspection (read-only)
- Packagist dcat/laravel-admin: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dcat/laravel-admin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-37x3-j9jq-vrjx (GitHub-reviewed advisory GHSA-37x3-j9jq-vrjx lists affected ranges: Packagist dcat/laravel-admin >=2.2.0-beta =2.2.2-beta <=2.2.2-beta)

Commands are suggestions: review each one before running it.

Loading voting…