dbcve.org
Drupal CanvasDrupal extension · Drupal Canvas Project

CVE-2026-58588

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 1.4.2 / 1.5.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 Drupal Drupal Canvas allows Cross-Site Scripting (XSS). This issue affects Drupal Canvas versions: from 0.0.0 to 1.4.2, from 1.5.0 to 1.5.2, from 1.6.0 to 1.6.1, from 1.7.0 to 1.7.1.

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 · high confidence

Cross-site scripting (XSS) vulnerability in Drupal Canvas module allows remote attackers to inject malicious JavaScript code through unsanitized user input that gets rendered in web pages without proper output encoding.

MitigationApply contextual output encoding to all user-supplied data before rendering in HTML/JavaScript contexts and update to a patched version when released.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Drupal CanvasDrupal extension
Affected:< 1.4.2>= 1.5.0, < 1.5.2>= 1.6.0, < 1.6.1>= 1.7.0, < 1.7.1

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
None

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

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 Drupal Canvas module is installed
    Locate the canvas module directory in your Drupal installation (typically in modules/contrib/canvas or modules/canvas) or run 'drush pm-list --status=enabled' to list enabled modules
    Affected if The Canvas module is present and enabled in the Drupal installation
  2. Identify installed Canvas module version
    Check the version number in the canvas.info.yml file located in the module directory, or run 'drush pm:info canvas' to retrieve version metadata
    Affected if The version is less than 1.4.2, or between 1.5.0 and 1.5.2 (exclusive), or between 1.6.0 and 1.6.1 (exclusive), or between 1.7.0 and 1.7.1 (exclusive)
  3. Verify the module renders user-supplied content
    Review how the Canvas module is being used on the site - check if any content types, fields, or views are configured to display data processed by the Canvas module in web page output
    Affected if The module is enabled and configured to render or display user-contributed data in HTML pages
  4. Inspect code for output encoding on user input
    Examine the module's PHP files (particularly form handlers and render functions) for use of output encoding functions like render(), drupal_render(), or Twig autoescape when handling user-supplied data
    Affected if User-supplied data is being output in HTML contexts without proper sanitization or contextual encoding functions

Your environment is affected if the Drupal Canvas module is installed at a version matching the affected ranges AND it is actively rendering unsanitized user input in web page output.

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.

dbcve · scoped
Upgrade available Upgrade to 1.4.2 / 1.5.2 / 1.6.1 or later
Fixed in 1.4.21.5.21.6.1
Interim mitigation

Apply contextual output encoding to all user-supplied data before rendering in HTML/JavaScript contexts and update to a patched version when released.

Recommended fix Moderate confidence

Upgrade to Drupal Canvas 1.7.1 or later (or the next available stable release beyond your current branch)

  1. 1. Identify the current version of Drupal Canvas installed in your environment.
  2. 2. Based on your current version, upgrade to the next available fixed release: if using <1.4.2, upgrade to 1.4.2 or later; if using 1.5.0-1.5.2, upgrade to 1.5.2 or later; if using 1.6.0-1.6.1, upgrade to 1.6.1 or later; if using 1.7.0-1.7.1, upgrade to 1.7.1 or later.
  3. 3. Test the upgrade in a non-production environment to verify compatibility with your Drupal installation.
  4. 4. Deploy the upgraded version to production after successful testing.
  5. 5. Verify the fix by confirming the installed version matches a fixed release (1.4.2, 1.5.2, 1.6.1, or 1.7.1+).
Caveat Review Drupal Canvas release notes for your target version to check for any breaking changes or required configuration updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Drupal Canvas Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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