CVE-2026-48000
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 · uneditedAdobe Commerce is affected by an Improper Redirect (Open Redirect) vulnerability that could result in a Security feature bypass. An attacker could construct a malicious URL that redirects a victim to an attacker-controlled site. Exploitation of this issue requires user interaction in that a victim must click on a malicious link. Scope is changed.
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 confidenceAdobe Commerce contains an Improper Redirect (Open Redirect) vulnerability that allows attackers to craft malicious URLs redirecting victims to attacker-controlled external sites. This can enable credential theft and account takeover through phishing. User interaction is required (clicking a malicious link).
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= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3= 2.4.6= 2.4.7= 2.4.8= 2.4.9>= 1.6.0, < 1.21.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Commerce or Magento versionCheck the composer.json file in the web root for the version declaration, or run a version lookup command if available for your deployment (e.g., checking the magento/product-community-edition or magento/enterprise-edition package version)Affected if The installed version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 for Adobe Commerce or Magento
-
Check for Adobe Commerce B2B module installationLocate the magento/module-b2b-core package in composer.json or check the vendor directory for B2B-specific modulesAffected if The B2B module version is 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3
-
Verify Adobe I/O Events version if installedCheck composer.json or package manager for adobe/io-events versionAffected if The installed version is 1.6.0 or higher but below 1.21.0
-
Confirm the redirect functionality is present and accessibleReview application code for redirect/forward handlers that accept user-controlled URL parameters (e.g., u, url, redirect, target, return_url parameters), or test by attempting a redirect with an external domain like example.comAffected if The application contains redirect logic that accepts external URLs without strict domain validation, which is the default behavior in affected versions
Your environment is affected if you are running any of the listed versions of Adobe Commerce, Adobe Commerce B2B, Adobe Magento, or Adobe I/O Events, and the application exposes redirect functionality to users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.21.0
Implement strict validation of redirect URLs to ensure they only point to internal or relative paths, rejecting any redirect to external domains. Apply any available vendor patches for Adobe Commerce.
Adobe Commerce 2.4.7-p1 or later; Magento Open Source 2.4.9-p1 or later; I/O Events 1.21.0 or later
- 1. Identify your exact Adobe Commerce/Magento version by running: php bin/magento --version
- 2. For Adobe Commerce 2.4.4-2.4.7: Upgrade to Adobe Commerce 2.4.7-p1 or later using composer: composer require magento/product-community-edition=2.4.7-p1 --no-update && composer update
- 3. For Magento Open Source 2.4.6-2.4.9: Upgrade to Magento 2.4.9-p1 or later using composer
- 4. For Adobe Commerce B2b 1.3.3-1.5.2: Upgrade to the corresponding patched version (2.4.7-p1 with compatible B2B module)
- 5. For I/O Events module >=1.6.0: Upgrade to version 1.21.0 or later via composer: composer require magento/module-shared-catalog=1.21.0 --no-update (adjust module name as needed)
- 6. After upgrade, clear cache: php bin/magento cache:clean
- 7. Reindex: php bin/magento indexer:reindex
- 8. Verify the upgrade was successful and test the redirect functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48000 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48000 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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