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

CVE-2026-56006

HIGH · 7.1 CVSS v3.1 Published 2026-06-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
Unauthenticated Cross Site Scripting (XSS) in H5P <= 1.17.6 versions.

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

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in H5P content creation framework versions 1.17.6 and below. Attackers can inject malicious scripts into the application without any authentication, potentially leading to session hijacking, credential theft, or phishing attacks against users.

MitigationUpgrade H5P to a version newer than 1.17.6 or apply the vendor-provided security patch to address the input validation/sanitization gap.

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. Confirm H5P is installed
    Search for H5P directories or files in the web root (commonly /h5p, /libraries/h5p, or integrated within CMS plugins/modules) or check the application's software inventory for H5P presence.
    Affected if H5P framework is present in the environment
  2. Identify the installed H5P version
    Locate the version file within the H5P installation (often named version.php, package.json, or h5p.version in the root H5P directory) or access the H5P admin interface which typically displays the version number.
    Affected if Unable to determine version or version cannot be retrieved
  3. Compare version to affected range
    Compare the identified version number to the affected range: versions 1.17.6 and below are vulnerable. If your version is 1.17.6 or lower, the environment falls within the affected range.
    Affected if Installed version is 1.17.6 or lower
  4. Verify unauthenticated access exposure
    Determine if the H5P content creation or interaction endpoints are accessible without authentication. Check if the application allows anonymous users to create, edit, or interact with H5P content.
    Affected if H5P content creation/input features are accessible to unauthenticated users

The environment is affected if H5P is installed with version 1.17.6 or below and the content creation/input features are accessible, allowing unauthenticated attackers to inject malicious scripts.

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

Upgrade H5P to a version newer than 1.17.6 or apply the vendor-provided security patch to address the input validation/sanitization gap.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56006 — 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-56006 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