dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-22524

HIGH · 7.1 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in themepassion Legacy Admin legacy-admin allows Reflected XSS.This issue affects Legacy Admin: from n/a through <= 9.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Reflected XSS vulnerability in themepassion Legacy Admin allows attackers to inject malicious JavaScript via unsanitized user input that gets reflected back in web pages. The flaw exists in the legacy-admin component affecting versions up to 9.5.

MitigationImplement proper input validation and output encoding for all user-supplied data before rendering in HTML context to prevent script execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify themepassion Legacy Admin installation
    Locate the legacy-admin component in your system. Check for directories or packages named 'legacy-admin' or 'themepassion-legacy-admin' in your web application root or application installation folder.
    Affected if The themepassion Legacy Admin component is present in your environment
  2. Determine the installed version of legacy-admin
    Locate version information for the legacy-admin component. Check configuration files, package manifests (e.g., composer.json, package.json), or a dedicated version file within the legacy-admin directory. Extract the version number.
    Affected if The installed version is 9.5 or any earlier version (versions up to and including 9.5 are affected)
  3. Verify legacy-admin component is enabled
    Confirm that the legacy-admin component is actually enabled and accessible in your web application configuration. Check routing, module加载, or admin panel configuration to determine if legacy-admin is active.
    Affected if The legacy-admin component is enabled and accessible via the web interface
  4. Confirm web interface accessibility
    Test whether the legacy-admin login or admin page is reachable over HTTP/HTTPS by accessing the legacy-admin endpoint. This could be at a path like /legacy-admin, /admin/legacy, or similar.
    Affected if The legacy-admin web interface is publicly or internally accessible without additional authentication controls

Your environment is affected if the legacy-admin component is installed, enabled, and running version 9.5 or earlier, making the unsanitized user input reflection possible in the web interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all user-supplied data before rendering in HTML context to prevent script execution.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22524 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data