Skip to main content
Vulnerability Database/CVE-2026-84914

CVE-2026-84914: Drupal Calculate Working Days Auth Bypass

CVE-2026-84914 is an authorization bypass vulnerability in Drupal Calculate Working Days module that enables forceful browsing attacks. This article covers the technical details, affected versions, security impact, and mitigation.

Published:

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-84914 Overview

CVE-2026-84914 is a Missing Authorization vulnerability [CWE-862] in the Drupal Calculate Working Days contributed module. The flaw allows forceful browsing, meaning unauthenticated or under-privileged users can access functionality that should be gated by access controls. The issue affects Calculate Working Days versions from 0.0.0 through 2.0.3. Drupal published the issue in security advisory SA-CONTRIB-2026-122. Site operators running the affected module should review exposure and apply the vendor-supplied fix.

Critical Impact

Unauthorized actors can reach module endpoints without passing authorization checks, exposing restricted functionality through direct URL access.

Affected Products

  • Drupal contributed module: Calculate Working Days
  • Versions 0.0.0 through 2.0.3
  • Drupal sites that have the module installed and enabled

Discovery Timeline

  • 2026-10-22 - CVE-2026-84914 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-84914

Vulnerability Analysis

The vulnerability is classified under CWE-862 (Missing Authorization). The Calculate Working Days module exposes routes or callbacks that do not enforce authorization checks before executing their logic. An attacker can access these endpoints by guessing or discovering the URL path, a technique commonly described as forceful browsing. Because the check is missing rather than merely weak, the attacker does not need to defeat a control; the control is absent. The scope of impact depends on which module functionality is exposed, but the pattern typically results in unauthorized data access or unauthorized state changes on the Drupal site.

Root Cause

The root cause is the absence of an access check on one or more module routes or controllers. In Drupal module development, routes defined in *.routing.yml or controller methods should declare _permission, _role, _access, or custom access callbacks. When these are missing or set permissively, Drupal serves the request to any caller that reaches the URL.

Attack Vector

An attacker sends an HTTP request directly to the vulnerable module endpoint. No authentication token, session, or elevated role is required to pass the missing check. Discovery can be performed through source code review of the public module, path enumeration, or crawling. The vendor advisory SA-CONTRIB-2026-122 is the authoritative source for the specific endpoint and exploitation preconditions. See the Drupal Security Advisory 2026-122 for module-specific technical details.

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 Attacks

Detection Methods for CVE-2026-84914

Indicators of Compromise

  • Unauthenticated HTTP requests in web server logs targeting Calculate Working Days module paths.
  • Requests to module endpoints originating from clients that have no established authenticated session cookie.
  • Spikes of 200-status responses to module routes from unexpected source IPs or user agents.

Detection Strategies

  • Review Drupal watchdog and web server access logs for module route access without a corresponding authentication event.
  • Compare request origins against expected administrative or staff IP ranges and flag anomalies.
  • Correlate access to module endpoints with user session identifiers to identify requests served to anonymous callers.

Monitoring Recommendations

  • Enable verbose access logging on the Drupal web tier for the duration of triage.
  • Forward web server and Drupal logs to a centralized logging platform for retention and query.
  • Alert on repeated requests to module endpoints from a single source within a short time window.

How to Mitigate CVE-2026-84914

Immediate Actions Required

  • Identify all Drupal sites with the Calculate Working Days module installed and record the installed version.
  • Upgrade the module to the fixed release referenced in SA-CONTRIB-2026-122.
  • If an upgrade cannot be applied immediately, disable the module through the Drupal extension manager.
  • Review web server access logs for prior unauthorized access to module endpoints.

Patch Information

Drupal has published remediation guidance in Drupal Security Advisory 2026-122. Site operators should install the fixed version of the Calculate Working Days module as described in the advisory. Versions 0.0.0 through 2.0.3 are affected; apply the release above 2.0.3 as directed by the vendor.

Workarounds

  • Disable the Calculate Working Days module until a patched release is applied.
  • Restrict access to the module routes at the reverse proxy or web application firewall by IP allowlisting trusted administrative sources.
  • Require authentication at the perimeter for any path prefix associated with the module.
bash
# Example: disable the module via Drush, then update
drush pm:uninstall calculate_working_days
drush pm:update calculate_working_days
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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.