dbcve.org
Views Builk OperationsApplication · Drupal

CVE-2011-3373

MEDIUM · 6.1 CVSS v3.1 Published 2019-11-25
Fix available
A fix is available. Upgrade to after 6.x1.10 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
Drupal Views Builk Operations (VBO) module 6.x-1.0 through 6.x-1.10 does not properly escape the vocabulary help when the vocabulary has had user tagging enabled and the "Modify node taxonomy terms" action is used. A remote attacker could provide a specially-crafted URL that could lead to cross-site scripting (XSS) attack.

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 Views Bulk Operations (VBO) module versions 6.x-1.0 through 6.x-1.10 fails to properly escape vocabulary help text when user tagging is enabled and the 'Modify node taxonomy terms' action is used, allowing injection of malicious JavaScript via specially-crafted URLs.

MitigationUpdate the VBO module to version 6.x-1.11 or later. If immediate updating is not feasible, disable the 'Modify node taxonomy terms' action and restrict vocabulary user tagging until the patch can be applied.

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
Views Builk OperationsApplication
Affected:>= 6.x-1.0, <= 6.x1.10

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. Locate the VBO module installation
    Check your Drupal modules directory (typically sites/all/modules/ or sites/all/modules/contrib/) for a folder named views_bulk_operations. Confirm its presence in your codebase.
    Affected if The views_bulk_operations module folder exists in your Drupal installation
  2. Identify the installed VBO version
    Open the views_bulk_operations.info file inside the module folder and read the version line, or query the Drupal system table: SELECT schema_version FROM system WHERE name = 'views_bulk_operations'; Compare this version against the 6.x-1.0 through 6.x-1.10 range.
    Affected if The installed version falls within 6.x-1.0 to 6.x-1.10 inclusive
  3. Verify the Modify node taxonomy terms action is enabled
    Navigate to Administer > Site building > Views > VBO actions (or access via /admin/build/views/tools), and check whether the 'Modify node taxonomy terms' action is listed as enabled or available in your VBO configuration.
    Affected if The 'Modify node taxonomy terms' action is enabled or available in VBO
  4. Check if user tagging is enabled on any vocabulary
    Go to Administer > Content management > Taxonomy > List vocabularies (or /admin/content/taxonomy), click each vocabulary's 'edit' link, and inspect the 'Content types' settings page for the 'Tags' checkbox or user tagging configuration.
    Affected if User tagging is enabled on one or more vocabularies (the "Users can create tags" or similar option is checked)

You are affected if VBO module version 6.x-1.0 through 6.x-1.10 is installed AND the 'Modify node taxonomy terms' action is being used AND user tagging is enabled on any vocabulary.

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.

From vendor data
Upgrade available Upgrade to a release after 6.x1.10
Interim mitigation

Update the VBO module to version 6.x-1.11 or later. If immediate updating is not feasible, disable the 'Modify node taxonomy terms' action and restrict vocabulary user tagging until the patch can be applied.

Fix this in Views Builk Operations Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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