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

CVE-2026-112040: Diem Project Open Redirect Vulnerability

CVE-2026-112040 is an open redirect flaw in diem-project diem affecting the Sign-In component. Attackers can exploit this via the Referer argument to redirect users to malicious sites. This article covers technical details, impact analysis, and recommended security measures.

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

CVE-2026-112040 is an open redirect vulnerability [CWE-601] in the diem-project diem content management framework. The flaw resides in the Sign-In component, specifically in dmCorePlugin/plugins/dmUserPlugin/modules/dmUser/lib/BasedmUserActions.class.php. Attackers manipulate the HTTP Referer header to redirect authenticated users to attacker-controlled destinations after sign-in. The vulnerability affects diem builds up to commit 116974edfb9a5b8bd69cb13586dc62bcdbb485ad. Because the project uses a rolling release model, specific affected version numbers are not enumerated. Public disclosure of the exploit has occurred, and the maintainers had not responded to the issue report at the time of publication.

Critical Impact

Attackers can craft malicious sign-in URLs that redirect users to phishing or malware-hosting domains, enabling credential theft campaigns that appear to originate from the trusted diem application.

Affected Products

  • diem-project diem up to commit 116974edfb9a5b8bd69cb13586dc62bcdbb485ad
  • dmUserPlugin module within dmCorePlugin
  • Any downstream application embedding the vulnerable Sign-In handler

Discovery Timeline

  • 2026-10-19 - CVE-2026-112040 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-112040

Vulnerability Analysis

The vulnerability is a classic unvalidated redirect [CWE-601] in the diem sign-in workflow. The BasedmUserActions controller consumes the HTTP Referer header to determine where to send the user after successful authentication. The handler does not validate the target against an allowlist of trusted hosts or restrict redirection to same-origin URLs. An attacker who controls the Referer value, typically by luring a user through a crafted link, can direct the post-authentication redirect to an arbitrary external domain. User interaction is required because the victim must click the attacker-supplied link and complete sign-in.

Root Cause

The root cause is missing destination validation in the sign-in action logic contained in BasedmUserActions.class.php. The handler trusts the inbound Referer as an opaque navigation hint and passes it directly to the redirect routine. There is no scheme check, host allowlist, or relative-path enforcement before issuing the HTTP 302 response.

Attack Vector

Exploitation is remote and performed over the network. The attacker crafts a URL that targets the vulnerable sign-in endpoint and causes a controlled Referer value to be sent, for example through a hyperlink hosted on an attacker-controlled page. After the victim authenticates, the diem application issues a redirect to the attacker's domain. The destination can host a cloned diem login page to harvest credentials or serve malware under the perceived trust of the originating site. See the GitHub Issue #457 Discussion and the VulDB CVE-2026-112040 entry for additional technical context.

Detection Methods for CVE-2026-112040

Indicators of Compromise

  • HTTP requests to the diem sign-in endpoint containing a Referer header pointing to an external, non-allowlisted host.
  • Web server logs showing 302 responses from the sign-in action with Location values that resolve to unrelated domains.
  • Spikes in sign-in traffic sourced from URL shorteners or newly registered domains correlated with user reports of unexpected redirects.

Detection Strategies

  • Instrument web application firewall (WAF) rules to flag requests where the Referer header host does not match the application's own host set.
  • Add server-side logging to the diem sign-in handler to record the raw Referer value and the resulting redirect target for later correlation.
  • Hunt in proxy and DNS telemetry for user navigation patterns that start on the diem sign-in URL and end on untrusted external domains within the same session.

Monitoring Recommendations

  • Alert on anomalous outbound redirect destinations tied to the dmUser module path /dmUser/ or equivalent routing prefix.
  • Correlate authentication success events with the subsequent redirect Location to identify suspicious post-login navigation.
  • Monitor abuse mailboxes and threat intel feeds for phishing lures that reference the organization's diem-hosted login URL.

How to Mitigate CVE-2026-112040

Immediate Actions Required

  • Audit all deployments running diem-project diem builds at or before commit 116974edfb9a5b8bd69cb13586dc62bcdbb485ad and inventory exposed sign-in endpoints.
  • Deploy a WAF rule that strips or rewrites the Referer header to a safe default when it points to an external host on requests to the sign-in action.
  • Educate users and support staff to inspect the post-login URL and report unexpected redirects away from the diem application.

Patch Information

No vendor patch has been published at the time of writing. The project uses a rolling release strategy and, according to the advisory, had not responded to the upstream issue report. Track remediation progress on the GitHub Diem Project Repository and the referenced GitHub Issue #457 Discussion.

Workarounds

  • Modify BasedmUserActions.class.php locally to validate the Referer value against an allowlist of trusted hosts before passing it to the redirect routine.
  • Replace Referer-based post-login redirection with a server-maintained session attribute that stores only relative paths originating from the application.
  • Enforce a Content Security Policy (CSP) and Referrer-Policy: same-origin to reduce the attacker's ability to seed external Referer values during sign-in flows.
  • Place the sign-in endpoint behind a reverse proxy rule that rejects requests whose Referer host is not in the organization's approved list.

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.