Security readout for executives and security teams
Plain-English summary
This is a legacy Drupal 6 module XSS issue in Views Bulk Operations. If an affected site uses the vulnerable taxonomy-term modification workflow, a remote attacker could trick a user into opening a crafted URL that runs script in the site context.
Executive priority
Treat as a targeted legacy-platform cleanup item. It is not shown as actively exploited in the supplied sources, but affected Drupal 6 systems can create session and content integrity risk if privileged users are exposed.
Technical view
CVE-2011-3373 affects Drupal Views Bulk Operations 6.x-1.0 through 6.x-1.10. The module did not properly escape vocabulary help when user tagging was enabled and the “Modify node taxonomy terms” action was used, allowing cross-site scripting via a specially crafted URL.
Likely exposure
Exposure is likely limited to legacy Drupal 6 sites running VBO 6.x-1.0 through 6.x-1.10 with user tagging enabled and the affected taxonomy-term modification action in use.
Exploitation context
The provided sources describe a remotely triggerable XSS condition through a crafted URL. The bundle does not identify active exploitation, public weaponization, CVSS scoring, or CISA KEV inclusion.
Researcher notes
The evidence is specific but incomplete: no CVSS vector, CWE, exploit maturity, or fixed version is included in the bundle. Focus validation on the exact module version and the taxonomy workflow described by the CVE.
Mitigation direction
- Inventory Drupal 6 sites using Views Bulk Operations.
- Identify VBO versions 6.x-1.0 through 6.x-1.10.
- Check Drupal or vendor guidance for the corrected release or supported replacement.
- Disable the affected action or module if it is not required.
- Retire or isolate unsupported Drupal 6 deployments where feasible.
Validation and detection
- Confirm whether Views Bulk Operations is installed and enabled.
- Check the installed VBO version against 6.x-1.0 through 6.x-1.10.
- Review taxonomy vocabularies for user tagging enabled.
- Confirm whether “Modify node taxonomy terms” is available to users.
- Validate remediation by confirming the vulnerable version is no longer present.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2011-3373 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3373CVE reference · x_refsource_MISC
- https://access.redhat.com/security/cve/cve-2011-3373CVE reference · x_refsource_MISC
- https://www.openwall.com/lists/oss-security/2011/09/22/4CVE reference · x_refsource_MISC
- https://www.securityfocus.com/bid/49727CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.