CVE-2024-28396
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 · uneditedAn issue in MyPrestaModules ordersexport v.6.0.2 and before allows a remote attacker to execute arbitrary code via the download.php component.
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 confidenceA remote code execution vulnerability exists in the download.php component of the MyPrestaModules ordersexport module for PrestaShop versions 6.0.2 and prior. Attackers can exploit this to execute arbitrary code on the affected server, likely due to improper input validation or unsafe file operations within the download functionality.
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<= 6.0.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Verify if ordersexport module is installedAccess PrestaShop admin panel, navigate to Modules > Modules and Services, and search for 'ordersexport' or 'Orders Export' to confirm the module is present in the installation.Affected if The ordersexport module is found and enabled on the PrestaShop installation.
-
Check the installed module versionIn PrestaShop admin, locate the ordersexport module details page and verify the version number displayed. Alternatively, inspect the module's main PHP file (typically in /modules/ordersexport/ or similar naming) for a version constant or header comment.Affected if The module version is 6.0.2 or lower.
-
Locate and verify download.php existsCheck for the presence of download.php file within the ordersexport module directory structure, typically found under /modules/ordersexport/controllers/front/download.php or similar path.Affected if The download.php file exists in the ordersexport module directory.
-
Inspect download.php for accessible endpointsReview web server access logs or attempt a direct HTTP request to the download.php endpoint (such as /module/ordersexport/download or /modules/ordersexport/controllers/front/download.php) to confirm it is reachable without authentication.Affected if The download.php endpoint is accessible without requiring admin authentication.
-
Check for unauthorized file modificationsCompare the md5sum or hash of download.php against a known clean version from the official source, or manually inspect the file for suspicious code patterns such as base64_decode, eval, shell_exec, or unserialize calls in the download handling logic.Affected if The download.php file contains suspicious code execution functions or has been modified from the original distribution.
The environment is affected if the ordersexport module is installed with version 6.0.2 or lower and the download.php component is accessible, as this combination allows the RCE vulnerability to be exploited.
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.
From vendor dataUpdate to the latest version of MyPrestaModules ordersexport once a patch is released. If no patch is available, disable the ordersexport module or restrict access to download.php via web server configuration until remediation is possible.
- 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-28396 — 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-28396 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