CVE-2024-34110
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 Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitrary code execution. A high-privilege attacker could exploit this vulnerability by uploading a malicious file to the system, which could then be executed. 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 · moderate confidenceAdobe Commerce contains an unrestricted file upload vulnerability allowing high-privilege authenticated attackers to upload malicious files (e.g., PHP shells) to the system. The uploaded files can then be executed for arbitrary code execution. No user interaction is required for exploitation.
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 Adobe Commerce or Magento installation versionRun 'bin/magento --version' from the Magento root directory, or inspect composer.json for the 'magento/product-community-edition' or 'magento/enterprise-edition' version entryAffected if The installed version matches 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, or 2.4.6 (for Adobe Commerce) or 2.4.4, 2.4.5, 2.4.6, 2.4.7 (for Magento)
-
Check Adobe Commerce Webhooks module versionRun 'bin/magento module:status Magento_Webhook' to confirm the module is enabled, then locate the module version in composer.json under vendor/magento/module-webhook or via 'composer show magento/module-webhook'Affected if The Webhooks module version is between 1.2.0 and 1.4.0 inclusive, indicating the vulnerable component is present
-
Inspect upload directories for suspicious executable filesSearch web-accessible directories (pub/media, var, pub/) for recently created PHP, PHTML, or other script files using 'find pub/media var -type f -name "*.php" -mtime -30' or similarAffected if Unexpected PHP or executable files exist in upload directories, especially in locations that are web-accessible
-
Review web server logs for file upload API activityExamine access logs (typically in var/log/ or /var/log/apache2/nginx/) for POST requests to webhook or API endpoints, filtering for 'POST' methods and file upload-related paths within the last 30 daysAffected if Numerous or unusual POST requests to webhook endpoints are present from admin user accounts, indicating potential exploitation attempts
-
Check file permission settings on media directoriesRun 'ls -la pub/media/' and verify file permissions on upload directories; check if .htaccess or nginx.conf restrictions are properly configured to prevent script execution in pub/mediaAffected if Directories allow script execution (execute bit set on directories) or lack restrictions preventing PHP execution in web-accessible folders
The environment is affected if Adobe Commerce/Magento version falls within the listed vulnerable ranges AND the Webhooks module is installed, or if suspicious executable files exist in web-accessible upload directories indicating potential exploitation.
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 vendor security patches for the affected Adobe Commerce versions (2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8). Additionally, implement strict file type validation by inspecting file magic bytes, store uploads outside the webroot, and disable script execution permissions on upload directories.
Adobe Commerce/Magento 2.4.7 (latest 2.4.7.x release)
- 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version or checking composer.json
- 2. Review the Adobe Security Bulletin (helpx.adobe.com) for the specific patch required for your version
- 3. For Magento 2.4.4: Apply patch SUPEE-XXXXX or upgrade to 2.4.4-p9 or later
- 4. For Magento 2.4.5: Apply patch SUPEE-XXXXX or upgrade to 2.4.5-p8 or later
- 5. For Magento 2.4.6: Apply patch SUPEE-XXXXX or upgrade to 2.4.6-p6 or later
- 6. For Magento 2.4.7: Upgrade to the latest available 2.4.7.x release
- 7. For Adobe Commerce 2.3.7-2.4.2: Upgrade to a supported version (2.4.7 recommended)
- 8. For Commerce Webhooks 1.2.0-1.4.0: Update to Commerce Webhooks 1.4.1 or later if available, or include the webhooks module in your main Commerce upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34110 — 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-34110 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