IslandoraDrupal extension
CVE-2026-3215
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 Islandora allows Cross-Site Scripting (XSS).This issue affects Islandora: from 0.0.0 before 2.17.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 · high confidenceCross-site scripting (XSS) vulnerability in Drupal Islandora module where user-supplied input is not properly sanitized before being rendered in web pages, allowing attackers to inject malicious scripts that execute in the context of other users' browsers.
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
IslandoraDrupal extension
< 2.17.5CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Islandora module is installedCheck the Drupal modules administration page or look for the islandora directory in sites/all/modules or web/modulesAffected if Islandora module exists and is enabled in Drupal
-
Find installed Islandora versionCheck the version in the islandora.info.yml file or composer.json file within the Islandora module directoryAffected if Version is less than 2.17.5 (e.g., 2.17.4, 2.16.x, 2.15.x, etc.)
-
Verify XSS attack surface existsIdentify if Islandora exposes any user input fields (such as metadata forms, repository metadata entry, or user-generated content fields) that accept and display input back to users or administratorsAffected if User-controllable input fields exist in Islandora that accept data without explicit output encoding applied at display time
You are affected if Islandora module is installed with a version less than 2.17.5 AND any user-supplied input fields in Islandora are rendered in web pages without sanitization.
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 · scoped2.17.5
Update Islandora to version 2.17.5 or later to obtain the patched code, or implement output encoding/sanitization on user inputs if immediate patching is not feasible.
Islandora 2.17.5
- Backup your current Islandora installation and database before proceeding
- Download Islandora version 2.17.5 from the official Drupal Islandora repository or releases page
- If using Composer for Drupal dependency management, run: composer require islandora/islandora:2.17.5 or composer update islandora/islandora --prefer-dist
- Clear Drupal caches after upgrading: drush cr or through the Drupal admin interface
- Verify the upgrade was successful by checking the Islandora version in admin/reports/status
- Test that the Islandora functionality works as expected, particularly any areas that might involve user input that could be reflected in web pages
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Islandora
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3215 — 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-3215 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