dbcve.org
ColorboxDrupal extension · Colorbox Project

CVE-2025-3900

MEDIUM · 6.1 CVSS v3.1 Published 2025-04-23
Fix available
A fix is available. Upgrade to 2.1.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Colorbox allows Cross-Site Scripting (XSS).This issue affects Colorbox: from 0.0.0 before 2.1.3.

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

Cross-site Scripting (XSS) vulnerability in the Drupal Colorbox module allows attackers to inject malicious scripts into web pages through improper neutralization of user input during web page generation. The vulnerability affects Colorbox versions before 2.1.3.

MitigationUpgrade the Colorbox module to version 2.1.3 or later to resolve the XSS vulnerability. Alternatively, implement input sanitization on any user-supplied data rendered through Colorbox.

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
ColorboxDrupal extension
Affected:< 2.1.3

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. Identify the installed Colorbox module version
    Locate the Colorbox module directory in your Drupal installation (typically in modules/contrib/colorbox or modules/colorbox) and check the info.yml or info.txt file for the version number, or use Drush command: drush pm-list --status=enabled --type=module | grep colorbox
    Affected if The displayed version is lower than 2.1.3 or no version is listed (implying an older release)
  2. Verify Colorbox module is enabled
    Check if the Colorbox module is actively enabled in your Drupal site through the admin interface at /admin/modules or by running: drush pm-list --status=enabled --type=module
    Affected if The Colorbox module is listed as enabled and active on the site
  3. Determine if Colorbox displays user-supplied content
    Review your Drupal site's configuration and custom code that uses Colorbox to load or display content. Check Colorbox display settings at /admin/config/media/colorbox and inspect any views, fields, or custom modules that invoke colorbox functionality with dynamic content
    Affected if Colorbox is configured to display or load content that includes user-generated input, comments, profile data, or any user-supplied parameters without sanitization

You are affected if the Colorbox module version is below 2.1.3 AND the module is enabled AND it processes or displays user-supplied content through its display functionality.

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.3 or later
Fixed in 2.1.3
Interim mitigation

Upgrade the Colorbox module to version 2.1.3 or later to resolve the XSS vulnerability. Alternatively, implement input sanitization on any user-supplied data rendered through Colorbox.

Recommended fix High confidence

2.1.3

  1. 1. Backup your Drupal database and files before making any changes
  2. 2. Navigate to the Colorbox module directory in your Drupal installation
  3. 3. Update the Colorbox module to version 2.1.3 or later using your preferred method (composer, Drush, or manual download from drupal.org)
  4. 4. If using Drush, run: drush pm-update colorbox
  5. 5. After updating, clear the Drupal cache: drush cr
  6. 6. Verify the Colorbox module version shows 2.1.3 or higher in the Drupal admin UI at /admin/modules

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

Fix this in Colorbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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