dbcve.org
ObfuscateDrupal extension · Obfuscate Project

CVE-2026-6871

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 2.0.2 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 Obfuscate allows Cross-Site Scripting (XSS). This issue affects Obfuscate: from 0.0.0 before 2.0.2.

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

The Drupal Obfuscate module versions prior to 2.0.2 contain a Cross-Site Scripting (XSS) vulnerability where user-supplied input is not properly neutralized before being rendered in web pages, allowing attackers to inject malicious scripts.

MitigationUpdate the Obfuscate module to version 2.0.2 or later which contains the proper input sanitization fix.

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
ObfuscateDrupal extension
Affected:< 2.0.2

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 the Obfuscate module is installed
    Locate the Obfuscate module directory in your Drupal installation, typically under /modules/, /profiles/, or /sites/all/modules/. Look for a folder named 'obfuscate' containing the module files.
    Affected if The obfuscate module directory exists in your Drupal modules folder.
  2. Determine the installed version of the Obfuscate module
    Open the obfuscate.info.yml or obfuscate.info file within the obfuscate module directory and read the 'version' or 'core' and 'version' fields. Alternatively, check composer.json if installed via Composer.
    Affected if The version listed is below 2.0.2, or the version field is absent entirely.
  3. Verify the module is enabled in Drupal
    Run the Drupal command 'drush pm-list --status=enabled' or access the Extend administration page (/admin/modules) to confirm the Obfuscate module is listed as enabled.
    Affected if The Obfuscate module appears in the list of enabled modules.
  4. Identify content using Obfuscate field formatters
    Inspect content types and entity fields that use the Obfuscate module's field formatters. Check field display settings in /adminStructure/display or via Drush with 'drush field-info field' to see where obfuscate formatters are applied.
    Affected if Any content type or entity has a field configured to use an Obfuscate formatter for rendering user-submitted data.

Your environment is affected if the Obfuscate module version is below 2.0.2, the module is enabled, and it is configured to render user input in web pages.

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.0.2 or later
Fixed in 2.0.2
Interim mitigation

Update the Obfuscate module to version 2.0.2 or later which contains the proper input sanitization fix.

Recommended fix High confidence

2.0.2

  1. 1. Backup your Drupal site database and files before making any changes
  2. 2. Navigate to the Drupal administration panel at /admin/modules
  3. 3. Locate the Obfuscate module in the module list
  4. 4. Check for available updates for the Obfuscate module
  5. 5. If update to version 2.0.2 is available, click 'Update' to install it
  6. 6. Alternatively, if using Composer, run: composer update drupal/obfuscate --with-all-dependencies
  7. 7. After updating, clear Drupal cache at /admin/config/development/performance
  8. 8. Verify the module shows version 2.0.2 on the Extend page
Caveat Check module compatibility with your Drupal core version before upgrading; minor point releases typically have no breaking changes

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

Fix this in Obfuscate 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-6871 — 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-6871 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