CVE-2025-48446: Drupal Commerce Alphabank Redirect · Incorrect Authorization
Affects Drupal Commerce Alphabank RedirectSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Drupal Commerce Alphabank Redirect | Affected
| Fixed in– |
AI-suggested
Given the absence of an official patch at the time of this analysis, European organizations should implement the following specific mitigations: 1) Immediately audit and restrict access to the Commerce Alphabank Redirect module configuration and usage to trusted administrators only, minimizing exposure. 2) Implement strict web application firewall (WAF) rules to monitor and block suspicious redirect requests or anomalous traffic patterns targeting the payment redirection endpoints. 3) Conduct thorough code reviews and, if feasible, apply temporary custom authorization checks to enforce proper access controls around the redirect functionality. 4) Enhance user awareness training to recognize and avoid phishing attempts that could trigger the required user interaction for exploitation. 5) Monitor logs for unusual redirect activities or failed authorization attempts to detect early signs of exploitation. 6) Plan and prioritize upgrading to Commerce Alphabank Redirect version 1.0.3 or later as soon as it becomes available, ensuring the vulnerability is fully remediated. 7) Coordinate with payment processors and financial partners to establish additional transaction monitoring and fraud detection during the mitigation period.
Description
Incorrect Authorization vulnerability in Drupal Commerce Alphabank Redirect allows Functionality Misuse.This issue affects Commerce Alphabank Redirect: from 0.0.0 before 1.0.3.