dbcve.org
Colorbox InlineDrupal extension · Colorbox Inline Project

CVE-2026-8493

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Colorbox Inline allows Cross-Site Scripting (XSS). This issue affects Colorbox Inline: from 0.0.0 before 2.1.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 Colorbox Inline module allows attackers to inject malicious JavaScript through unsanitized input that gets rendered in web pages. This is a classic input validation failure where user-supplied data is not properly escaped before output.

MitigationUpdate Colorbox Inline module to version 2.1.1 or later to patch the XSS vulnerability. Before updating, ensure a complete backup of the Drupal site exists.

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
Colorbox InlineDrupal extension
Affected:< 2.1.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
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 checks

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

  1. Verify Drupal is installed
    Check for the presence of Drupal core files (e.g., index.php, update.php in the web root) or look for the 'Drupal' string in page source of any site URL.
    Affected if Drupal CMS is not present - the vulnerability only affects Drupal installations.
  2. Check if Colorbox Inline module is installed
    Look for the colorbox_inline module directory in sites/all/modules or modules/contrib. Alternatively, access /admin/modules or /admin/reports/status to list installed modules.
    Affected if The Colorbox Inline module is not installed - no action needed.
  3. Determine installed version of Colorbox Inline
    Locate the colorbox_inline.info.yml or colorbox_inline.info file inside the module directory and read the 'version' or 'core' field. Alternatively, check /admin/reports/status for the module version if displayed.
    Affected if The module version cannot be determined or is below 2.1.1.
  4. Compare version to affected range
    Parse the version from the .info.yml file and compare numerically against 2.1.1. For dev versions or git checkouts, check the CHANGELOG.txt or git tags for the latest release tag.
    Affected if Installed version is any release prior to 2.1.1 (e.g., 2.1.0, 2.0.x, 1.x).
  5. Confirm colorbox inline feature is in use
    Search Drupal content (nodes, blocks, views) for references to 'colorbox-inline' or 'colorbox inline' in field configurations. Check if any content types use a colorbox field formatter.
    Affected if The vulnerable colorbox inline functionality is actively used on the site, increasing exposure to the XSS flaw.

A user is affected if Drupal is running with the Colorbox Inline module installed at a version lower than 2.1.1 and the colorbox inline feature is enabled or used on the site.

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 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Update Colorbox Inline module to version 2.1.1 or later to patch the XSS vulnerability. Before updating, ensure a complete backup of the Drupal site exists.

Recommended fix Moderate confidence

2.1.1

  1. 1. Back up your Drupal database and files before making any changes.
  2. 2. Navigate to your Drupal site's root directory.
  3. 3. If using Composer for dependency management, run: composer require drupal/colorbox_inline:^2.1.1 to update to the fixed version.
  4. 4. Alternatively, if using Drupal's UI, go to Extend > Check for updates and update the Colorbox Inline module to version 2.1.1.
  5. 5. Clear Drupal caches after upgrading: drush cr or via admin UI at Configuration > Development > Performance > Clear all caches.
  6. 6. Verify the update was successful by checking the module version at Extend > Colorbox Inline.
Caveat Review any custom configurations or overrides for Colorbox Inline after upgrade, as minor version upgrades typically do not introduce breaking changes but may have altered default behaviors.

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

Fix this in Colorbox Inline Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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