dbcve.org
FacetsDrupal extension · Facets Project

CVE-2024-13283

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 2.0.9 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 Facets allows Cross-Site Scripting (XSS).This issue affects Facets: from 0.0.0 before 2.0.9.

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 confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the Drupal Facets module where user-supplied input is not properly neutralized before being rendered in web pages. This allows authenticated attackers to inject malicious JavaScript code that executes in the browsers of users viewing Facets-generated content.

MitigationUpgrade Drupal Facets module to version 2.0.9 or later. Until patched, sanitize all user input and output encoding should be applied to Facets widget 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
FacetsDrupal extension
Affected:< 2.0.9

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. Verify Facets module is installed
    In the Drupal admin interface, navigate to Extend or use Drush command 'drush pm-list --status=enabled' to list enabled modules and confirm the Facets module is present.
    Affected if Facets module is not installed or not enabled - not affected
  2. Determine the installed Facets module version
    Check the module's .info.yml file in the modules/facets directory, or run 'drush pm:list --format=json' to see version details, or look at the composer.json file if managed by Composer.
    Affected if Version is 2.0.9 or higher - not affected; version is below 2.0.9 - potentially affected
  3. Confirm Facets widgets are in use
    Navigate to the Drupal Facets administration page (typically at /admin/config/search/facets) and list all configured facet widgets to see if any are actively displaying content on the site.
    Affected if No Facets widgets are configured or in use - not affected
  4. Check if user-supplied input is rendered through Facets
    Inspect the facet configurations to determine what data source the facets are processing. If facets display user-contributed content (such as taxonomy terms, user profiles, or user-generated data), the injected script could be stored and rendered when users view the facet blocks.
    Affected if Facets display user-supplied content without sanitization - likely affected

The environment is affected only if the Facets module is installed with a version below 2.0.9 and Facets widgets are actively displaying user-supplied content that is rendered 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.9 or later
Fixed in 2.0.9
Interim mitigation

Upgrade Drupal Facets module to version 2.0.9 or later. Until patched, sanitize all user input and output encoding should be applied to Facets widget content.

Recommended fix High confidence

2.0.9

  1. 1. Back up your Drupal site database and files
  2. 2. Update the Facets module to version 2.0.9 or later using Composer (composer require drupal/facets:^2.0.9) or your site's update method
  3. 3. Run database updates if required (drush updatedb or via admin UI)
  4. 4. Clear Drupal caches (drush cr)
  5. 5. Verify the Facets module shows version 2.0.9 or higher at admin/modules
  6. 6. Test Facets functionality to ensure the XSS vulnerability is resolved and the module works correctly
Caveat Check Drupal core and other module compatibility before upgrading; minor version updates typically have minimal breaking changes

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

Fix this in Facets Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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