Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-84921 Overview
CVE-2026-84921 is a missing authorization vulnerability [CWE-862] in the Drupal Webform Submissions Delete contributed module. The flaw allows unauthorized users to perform forceful browsing against webform submission deletion endpoints. Affected versions range from 0.0.0 through 1.2.0. The module fails to verify that a requesting user holds the required permissions before processing deletion operations against webform submissions. Site administrators relying on this module to manage webform submissions should treat the issue as a direct access-control bypass against submission data lifecycle controls.
Critical Impact
Unauthorized actors can access deletion workflows for webform submissions by directly requesting restricted URLs, bypassing intended permission checks on the Drupal site.
Affected Products
- Drupal contributed module: Webform Submissions Delete
- Versions 0.0.0 through 1.2.0
- Drupal sites that enable the module and expose submission management routes
Discovery Timeline
- 2026-10-22 - CVE-2026-84921 published to the National Vulnerability Database
- 2026-10-22 - Last updated in the NVD database
- Reference: Drupal Security Advisory SA-CONTRIB-2026-133
Technical Details for CVE-2026-84921
Vulnerability Analysis
The Webform Submissions Delete module provides functionality to remove webform submission records from a Drupal site. The vulnerable code paths do not enforce an authorization check before executing the deletion handler. An unauthenticated or low-privilege user can request the deletion route directly and trigger behavior that should be restricted to privileged roles. This is a classic forceful browsing scenario in which route-level and object-level permission checks are missing from the request handling flow. Because the issue sits in the authorization layer rather than input handling, standard input validation defenses do not block the attack. The vulnerability is tracked under CWE-862: Missing Authorization.
Root Cause
The module omits a permission check, such as a _permission route requirement or an access callback, on the controller or form handler that processes submission deletions. Drupal's access API requires module authors to explicitly declare permissions for routes and entity operations. When those declarations are absent, Drupal defaults to permitting the request, which is the condition exploited here.
Attack Vector
An attacker enumerates or guesses the URL pattern used by the module to delete webform submissions. They issue an HTTP request to that endpoint with a target submission identifier. The site processes the request without verifying the caller's role or permission. See the Drupal Security Advisory for vendor-provided technical details.
// No verified exploit code is published for this issue.
// Attack pattern (conceptual):
// GET or POST to the module's submission delete route
// with a valid submission ID, without the required permission.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-84921
Indicators of Compromise
- Unexpected deletions of webform submission records in the Drupal database or admin logs
- Requests to submission deletion routes originating from unauthenticated sessions or non-administrative accounts
- Gaps in webform submission identifiers that correlate with external HTTP requests in access logs
Detection Strategies
- Review Drupal watchdog and dblog entries for submission deletion events and correlate them with the acting user account
- Inspect web server access logs for direct requests to routes exposed by the Webform Submissions Delete module
- Alert on deletion requests served with HTTP 200 responses to users lacking administrative roles
Monitoring Recommendations
- Forward Drupal application logs and web server access logs to a centralized logging platform for retention and query
- Create detection rules that flag high-volume or anomalous DELETE or form-submit actions against webform submission endpoints
- Baseline normal administrative activity so that forceful browsing patterns stand out against expected traffic
How to Mitigate CVE-2026-84921
Immediate Actions Required
- Inventory Drupal sites to identify installations of the Webform Submissions Delete module at version 1.2.0 or earlier
- Upgrade to a fixed release as published in Drupal Security Advisory SA-CONTRIB-2026-133
- Audit webform submission records for unauthorized deletions since the module was deployed
Patch Information
Refer to the Drupal Security Advisory SA-CONTRIB-2026-133 for the fixed version and upgrade guidance. Apply the vendor-provided update to restore proper permission enforcement on submission deletion routes.
Workarounds
- Disable the Webform Submissions Delete module until the patched release can be installed
- Restrict access to webform submission management paths at the reverse proxy or web application firewall layer
- Limit anonymous access to administrative URL patterns associated with the module
# Example: disable the module via Drush until a patched version is installed
drush pm:uninstall webform_submissions_delete
drush cache:rebuild
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

