ObfuscateDrupal extension · Drupal
CVE-2025-3130
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 Obfuscate allows Stored XSS.This issue affects Obfuscate: from 0.0.0 before 2.0.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 confidenceStored Cross-site Scripting (XSS) vulnerability in Drupal's Obfuscate module allows attackers to inject malicious scripts through improper input neutralization. The vulnerability is stored (persistent), meaning the malicious payload is saved on the server and executed when other users view the affected content.
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
< 2.0.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
- 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.
-
Check installed Obfuscate module versionLocate the Obfuscate module directory (typically in modules/contrib/obfuscate or modules/custom/obfuscate) and examine the info.yml file or composer.json to find the current version number.Affected if The version is below 2.0.1 (e.g., 2.0.0, 1.x.x, or unversioned)
-
Verify Obfuscate module is enabledIn the Drupal admin interface, navigate to Extend or use drush pm-list --type=module to confirm the Obfuscate module is installed and enabled.Affected if The module shows as enabled or installed
-
Identify content types using Obfuscate fieldsReview field configuration at Structure > Content Types > [type] > Manage Fields, or inspect the field storage configuration in the database (config table) for fields with type 'obfuscate' or field_type referencing obfuscation.Affected if Any content type has fields configured to use the Obfuscate widget or formatter
-
Check form displays using ObfuscateInspect view modes and form displays at Structure > Content Types > [type] > Manage Form Display and Manage Display to see if Obfuscate formatters are assigned to any fields.Affected if Obfuscate formatters are assigned to visible fields that store user-supplied data
-
Review recent content for unexpected scriptsQuery the database for recent node revisions or check the node_content table for any script tags or HTML in fields that use obfuscation, or examine recent content entries through the admin content list.Affected if Malicious script payloads (script tags, event handlers, javascript: URIs) are found in fields that should contain obfuscated data
The environment is affected if the Obfuscate module version is below 2.0.1 and the module is enabled with any fields or content types using obfuscation functionality.
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.0.1
Update the Drupal Obfuscate module to version 2.0.1 or later to patch the input validation flaw. Review existing content for any injected malicious scripts.
2.0.1
- Back up your Drupal site database and files
- Update the Obfuscate module using Composer: composer require drupal/obfuscate:^2.0.1
- Run database updates: drush updatedb (or via admin UI at /update.php)
- Clear Drupal caches: drush cr (or via admin UI at /admin/config/development/performance)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Obfuscate
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3130 — 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-2025-3130 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