dbcve.org
Commerce Eurobank \(redirect\)Drupal extension · Commerce Eurobank \(redirect\) Project

CVE-2025-48445

HIGH · 8.8 CVSS v3.1 Published 2025-06-11
Fix available
A fix is available. Upgrade to 2.1.1 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 Eurobank (Redirect) allows Functionality Misuse.This issue affects Commerce Eurobank (Redirect): from 0.0.0 before 2.1.1.

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 · moderate confidence

An Incorrect Authorization vulnerability in the Drupal Commerce Eurobank (Redirect) payment module allows attackers to misuse functionality through improper authorization checks. The vulnerability affects all versions prior to 2.1.1 and enables unauthorized access to certain payment operations.

MitigationUpgrade the Drupal Commerce Eurobank (Redirect) module to version 2.1.1 or later to remediate the authorization bypass.

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 Eurobank \(redirect\)Drupal extension
Affected:>= 2.0.0, < 2.1.1

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. Identify if the Commerce Eurobank (redirect) module is installed
    Check your Drupal installation for the presence of the Eurobank Redirect payment module. This is typically found in web/modules/contrib/commerce_eurobank or similar directory under your Drupal modules folder.
    Affected if The module directory exists in your Drupal modules/contrib path
  2. Check the installed module version
    Locate the composer.json or info.yml file within the commerce_eurobank module directory and read the version number. Alternatively, run 'composer show drupal/commerce_eurobank' if installed via Composer.
    Affected if The reported version is less than 2.1.1 (e.g., 2.0.0 through 2.1.0)
  3. Verify if the module is enabled in Drupal
    Log into your Drupal administration panel and navigate to Extend (or use Drush: 'drush pm-list --status=enabled' and filter for eurobank). Check if the Eurobank Redirect payment module is listed as enabled.
    Affected if The module shows as enabled/active in your Drupal site configuration

Your environment is affected if the Commerce Eurobank (redirect) module is installed, enabled, and its version is 2.0.0 through 2.1.0 (prior to 2.1.1).

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 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade the Drupal Commerce Eurobank (Redirect) module to version 2.1.1 or later to remediate the authorization bypass.

Recommended fix Moderate confidence

2.1.1

  1. 1. Back up your Drupal site database and files before making any changes
  2. 2. Update the Commerce Eurobank (Redirect) module to version 2.1.1 using Composer: composer update drupal/commerce_eurobank_redirect --with-all-dependencies
  3. 3. Alternatively, download version 2.1.1 from www.drupal.org/project/commerce_eurobank_redirect and install via the Drupal admin interface or drush
  4. 4. Run database updates if required: drush updatedb or via the admin interface at /update.php
  5. 5. Clear Drupal caches: drush cache-clear all or via the admin interface
  6. 6. Verify the module is updated to 2.1.1 on the Extend (Modules) page
  7. 7. Test the Eurobank redirect payment functionality to ensure authorization controls are working correctly

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

Fix this in Commerce Eurobank \(redirect\) Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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