CVE-2024-34108
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 versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction, but admin privileges are required and 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 · high confidenceAdobe Commerce contains an improper input validation vulnerability that allows authenticated administrators to achieve arbitrary code execution. The vulnerability involves insufficient validation of user-supplied input that enables code injection or execution in the context of the current user session, with a scope change indicating potential privilege escalation beyond normal admin capabilities.
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.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6>= 1.2.0, <= 1.4.0= 2.4.4= 2.4.5= 2.4.6= 2.4.7CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Commerce or Magento versionRun command: php bin/magento --version or check composer.json for version entryAffected if Version equals 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, or 2.4.7 (for Magento)
-
Check Adobe Commerce Webhooks module versionRun: composer show magento/module-webhooks 2>/dev/null | grep version OR check vendor/magento/module-webhooks/composer.jsonAffected if Webhooks module version is between 1.2.0 and 1.4.0 inclusive
-
Verify if Webhooks module is enabledRun: php bin/magento module:status | grep Webhooks OR check app/etc/config.php for Magento_Webhooks setting value of 1Affected if Magento_Webhooks module is enabled (value = 1)
-
Audit admin user accounts for unauthorized creationsRun SQL: SELECT * FROM admin_user WHERE created > expected_date OR check admin_user table for unknown admin accounts with elevated privilegesAffected if New or unexpected admin accounts exist that were not created by known administrators
-
Review admin session activity and API token usageCheck admin_user_session table or webhooks API logs in var/log for unexpected admin actions, especially suspicious payload executionsAffected if Admin sessions show code execution attempts or API calls with suspicious injection patterns in webhook payloads
User is affected if their Adobe Commerce/Magento version is 2.4.0-2.4.6 (or 2.3.7/2.4.7 for Magento) AND the Adobe Commerce Webhooks module version 1.2.0-1.4.0 is enabled, or if unauthorized admin accounts or code injection attempts are found in the environment.
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 · scopedApply the relevant Adobe security patches or upgrade to a patched version of Adobe Commerce (2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 or later). Review admin user accounts and audit recent admin activity for signs of exploitation.
Upgrade to latest available patch version (2.4.4-p9+, 2.4.5-p8+, 2.4.6-p6+, or 2.4.7-p1+)
- 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
- 2. Create a full backup of your database and files before proceeding with any upgrade
- 3. For Adobe Commerce 2.4.4.x: upgrade to 2.4.4-p9 or later by running: composer require magento/product-community-edition=2.4.4-p9 --no-update && composer update
- 4. For Adobe Commerce 2.4.5.x: upgrade to 2.4.5-p8 or later by running: composer require magento/product-community-edition=2.4.5-p8 --no-update && composer update
- 5. For Adobe Commerce 2.4.6.x: upgrade to 2.4.6-p6 or later by running: composer require magento/product-community-edition=2.4.6-p6 --no-update && composer update
- 6. For Adobe Commerce 2.4.7.x: upgrade to 2.4.7-p1 or later by running: composer require magento/product-community-edition=2.4.7-p1 --no-update && composer update
- 7. After composer update completes, run: bin/magento setup:upgrade
- 8. Clear caches: bin/magento cache:flush
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34108 — 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-2024-34108 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