dbcve.org
CommerceApplication · Adobe

CVE-2025-24409

HIGH · 8.2 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized access, leading to both a High impact to confidentiality and Low impact to integrity. Exploitation of this issue does not require user interaction.

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

Adobe Commerce contains an Incorrect Authorization vulnerability allowing attackers to bypass security measures and gain unauthorized access. The flaw affects multiple versions (2.4.4-p11 through 2.4.8-beta1) and enables security feature bypass with High confidentiality impact and Low integrity impact. No user interaction is required for exploitation.

MitigationApply the vendor-provided security patch or upgrade to a patched Adobe Commerce version. Review and validate all authorization controls after applying the update.

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
CommerceApplication
Affected:< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0
MagentoCMS
Affected:< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8

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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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 the installed Adobe Commerce or Magento version
    Run the command: php bin/magento --version or check the composer.json file for the version entry
    Affected if The version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8 (including beta), or any version below 2.4.4
  2. Check if Adobe Commerce B2B module is installed
    Run: php bin/magento module:status Magento_Company or inspect the app/etc/config.php file for Magento_Company module status
    Affected if B2B module is present and its version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0, or any version below 1.3.3
  3. Review admin user accounts for unauthorized creation
    Navigate to System > Permissions > All Users in the admin panel or query the admin_user table in the database
    Affected if Unexpected admin accounts exist that were not created by authorized administrators
  4. Audit security configuration settings
    Check Stores > Configuration > Security settings or review the core_config_data table for modified security-related configurations
    Affected if Security settings have been altered from their expected values or unauthorized access configurations are present

Your environment is affected if you are running Adobe Commerce or Magento versions 2.4.4 through 2.4.8 (including beta), or any version prior to 2.4.4, or any affected B2B version (1.3.3 through 1.5.0 or below 1.3.3).

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.3.3 / 2.4.4 or later
Fixed in 1.3.32.4.4
Interim mitigation

Apply the vendor-provided security patch or upgrade to a patched Adobe Commerce version. Review and validate all authorization controls after applying the update.

Recommended fix High confidence

Upgrade to the latest available patch: 2.4.7-p3 (preferred) or 2.4.6-p8 or 2.4.5-p10 or 2.4.4-p11 depending on your current minor version branch

  1. 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. 2. Create a complete backup of your codebase, database, and media files before proceeding
  3. 3. Test the upgrade in a staging environment that mirrors production
  4. 4. Update composer.json to require the fixed patch version: For 2.4.4.x upgrade to 2.4.4-p11, for 2.4.5.x upgrade to 2.4.5-p10, for 2.4.6.x upgrade to 2.4.6-p8, or for 2.4.7.x upgrade to 2.4.7-p3
  5. 5. Run composer update to fetch the new packages: composer update
  6. 6. After composer update completes, clear the cache: bin/magento cache:clean
  7. 7. Run the upgrade scripts: bin/magento setup:upgrade
  8. 8. Re-index all data: bin/magento indexer:reindex
Caveat Patch upgrades typically have minimal breaking changes but review Adobe Commerce release notes for any deprecation notices; always test in staging first

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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