Drupal CanvasDrupal extension · Drupal Canvas Project
CVE-2026-58587
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 · uneditedImproper 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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in Drupal Canvas allows attackers to inject malicious JavaScript through unsanitized user input that gets rendered in web pages. The vulnerability exists in multiple versions due to improper input validation during web page generation.
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
< 1.4.2>= 1.5.0, < 1.5.2>= 1.6.0, < 1.6.1>= 1.7.0, < 1.7.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Drupal Canvas module versionLocate the module's .info.yml file (typically at /modules/canvas/drupal_canvas.info.yml or /sites/all/modules/canvas/drupal_canvas.info.yml) and read the 'version' or 'core' and 'project' fields. Alternatively, run: drush pm-list --type=module --status=enabled | grep -i canvasAffected if The version displayed falls within any of these ranges: < 1.4.2, >= 1.5.0 and < 1.5.2, >= 1.6.0 and < 1.6.1, or >= 1.7.0 and < 1.7.1
-
Verify the Canvas module is enabledCheck if the Canvas module is listed as enabled in Drupal's system table, or run: drush pm-list --type=module --status=enabledAffected if The Canvas module is installed and enabled on the Drupal site
-
Identify input handling filesExamine the Drupal Canvas module directory for files that handle form submissions or content rendering, typically in /modules/canvas/src/ or /modules/canvas/. Look for controllers, forms, or plugins that accept user inputAffected if Files exist that process user-submitted content through the Canvas module without apparent sanitization routines
-
Inspect the content rendering pathwayReview PHP files in the Canvas module that render stored content back to users, checking for output encoding functions like htmlspecialchars() or Drupal's render APIAffected if User-supplied data from the Canvas module is rendered in web pages without proper sanitization or encoding applied
You are affected if Drupal Canvas module is enabled and its installed version falls within the vulnerable ranges: < 1.4.2, 1.5.0-1.5.1, 1.6.0, or 1.7.0.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4.21.5.21.6.1
Update Drupal Canvas to the latest version beyond 1.7.1 that contains the security patch. Apply proper output encoding and input sanitization on all user-supplied data before rendering in the browser.
1.7.2 (or latest stable release)
- 1. Identify your current Drupal Canvas version by checking the composer.json file or the Drupal admin interface.
- 2. Determine which version branch you are on (1.4.x, 1.5.x, 1.6.x, or 1.7.x).
- 3. Run 'composer require drupal/canvas:1.7.2' or 'composer update drupal/canvas:1.7.2' to upgrade to the fixed version.
- 4. Clear Drupal caches after the upgrade using 'drush cr' or through the admin interface at /admin/config/development/performance.
- 5. Verify the upgrade was successful by checking the canvas module version at /admin/modules or via composer show drupal/canvas.
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
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-58587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58587 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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