dbcve.org
Quick EditDrupal extension · Wim Leers

CVE-2026-2348

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 1.0.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Quick Edit allows Cross-Site Scripting (XSS).This issue affects Quick Edit: from 0.0.0 before 1.0.5, from 2.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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Drupal's Quick Edit module. The vulnerability stems from improper neutralization of user input during web page generation, allowing authenticated attackers to inject malicious JavaScript that executes when other users interact with edited content.

MitigationUpdate Drupal Quick Edit module to version 1.0.5 or 2.0.1 or later to remediate the XSS vulnerability. Review and test Quick Edit functionality after applying the patch.

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
Quick EditDrupal extension
Affected:< 1.0.5= 2.0.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Quick Edit module installation
    Search for the quick_edit module directory in your Drupal installation, typically under modules/contrib/ or modules/ directory
    Affected if The Quick Edit module directory exists on the server
  2. Identify the installed version
    Open the quick_edit.info.yml or composer.json file in the module directory and read the version number
    Affected if The version is less than 1.0.5 or equals 2.0.0
  3. Verify the module is enabled
    Run Drupal command 'drush pm-list --status=enabled' or query the system table in the Drupal database for the quick_edit module entry with status=1
    Affected if The Quick Edit module appears in the list of enabled modules
  4. Confirm the module is accessible on the site
    Access /admin/content or any page that uses Quick Edit functionality and verify the module loads successfully
    Affected if The Quick Edit module is actively loaded and functional on the site

You are affected if the Quick Edit module is installed, enabled, and its version is either less than 1.0.5 or exactly 2.0.0, as this allows the stored XSS vulnerability to be triggered when users interact with edited content.

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 1.0.5 or later
Fixed in 1.0.5
Interim mitigation

Update Drupal Quick Edit module to version 1.0.5 or 2.0.1 or later to remediate the XSS vulnerability. Review and test Quick Edit functionality after applying the patch.

Recommended fix High confidence

Quick Edit 1.0.5 (for 1.x) or 2.0.1 (for 2.x)

  1. Determine the current version of the Quick Edit module by checking your Drupal installation's composer.json or the modules list
  2. If using Composer for Drupal module management, run: composer require drupal/quick_edit:1.0.5 (for 1.x branch) or composer require drupal/quick_edit:2.0.1 (for 2.x branch)
  3. If not using Composer, download the appropriate version from www.drupal.org/project/quick_edit
  4. Backup your database and files before applying the update
  5. Clear Drupal cache after upgrading: 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 Quick Edit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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