dbcve.org
Commerce Alphabank RedirectDrupal extension · Commerce Alphabank Redirect Project

CVE-2025-48446

HIGH · 8.8 CVSS v3.1 Published 2025-06-11
Fix available
A fix is available. Upgrade to 1.0.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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

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

An incorrect authorization vulnerability exists in the Drupal Commerce Alphabank Redirect payment module. The flaw allows authenticated users to misuse certain functionality by bypassing intended authorization checks, potentially enabling unauthorized actions within the payment processing workflow.

MitigationUpgrade the Alphabank Redirect module to version 1.0.3 or later to obtain the authorization fix. Before deploying, verify compatibility with the current Drupal Core version and thoroughly test the payment redirect functionality.

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
Commerce Alphabank RedirectDrupal extension
Affected:>= 1.0.1, < 1.0.3

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify if Alphabank Redirect module is installed
    List installed Drupal modules and search for 'commerce_alphabank_redirect' or check the modules/commerce_alphabank_redirect directory exists in the codebase
    Affected if The module is present in the Drupal installation
  2. Determine the installed module version
    Run 'drush pm:list' or check the module's info.yml file (modules/commerce_alphabank_redirect/commerce_alphabank_redirect.info.yml) for the version field, or check composer.json
    Affected if The version cannot be determined or is returned as null
  3. Compare version against vulnerable range
    Review the version identified in the previous step and compare it to the affected range: versions 1.0.1 through 1.0.2.x
    Affected if The installed version is 1.0.1, 1.0.2, or any 1.0.x version below 1.0.3
  4. Check if payment method is enabled
    Navigate to Drupal admin under Commerce > Configuration > Payment methods or run a database query on the 'commerce_payment_method' table to see if Alphabank Redirect is an active payment method
    Affected if The Alphabank Redirect payment method is enabled and configured for use

The environment is affected if the Commerce Alphabank Redirect module is installed with a version between 1.0.1 and 1.0.2.x inclusive, and the payment method is enabled.

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.3 or later
Fixed in 1.0.3
Interim mitigation

Upgrade the Alphabank Redirect module to version 1.0.3 or later to obtain the authorization fix. Before deploying, verify compatibility with the current Drupal Core version and thoroughly test the payment redirect functionality.

Recommended fix High confidence

1.0.3

  1. Backup your Drupal site and database before making any changes
  2. Update the Commerce Alphabank Redirect module to version 1.0.3 using Composer: `composer require drupal/commerce_alphabank_redirect:^1.0.3 --update-with-all-dependencies`
  3. Alternatively, update via the Drupal admin interface at /admin/modules or /admin/reports/status
  4. Clear the Drupal cache after the update using `drush cr` or via the admin interface at /admin/config/development/performance
  5. Verify the module version shows 1.0.3 at /admin/modules or /admin/reports/status

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Alphabank Redirect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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