PrestashopCMS
CVE-2024-34717
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 · uneditedPrestaShop is an open source e-commerce web application. In PrestaShop 8.1.5, any invoice can be downloaded from front-office in anonymous mode, by supplying a random secure_key parameter in the url. This issue is patched in version 8.1.6. No known workarounds are available.
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 confidencePrestaShop 8.1.5 contains an Insecure Direct Object Reference (IDOR) vulnerability in the invoice download functionality. The application fails to properly validate that the user requesting an invoice is authorized to access it - any invoice can be downloaded by providing a random secure_key parameter in the URL without authentication.
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
PrestashopCMS
= 8.1.5CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check installed PrestaShop versionAccess the PrestaShop admin panel, navigate to Advanced Parameters > Configuration Information to view the version number, or check the version in the application footer or in the config/settings.inc.php fileAffected if Version is exactly 8.1.5
-
Verify invoice PDF generation is enabledIn the PrestaShop admin panel, go to Modules > Module Manager and search for the PDF generator or invoice-related module. Check if it is installed and enabledAffected if Invoice PDF generation module is present and enabled
If running PrestaShop version 8.1.5 with the invoice PDF generation module enabled, the IDOR vulnerability in the invoice download is present.
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 · scopedUpgrade PrestaShop to version 8.1.6 or later to apply the patch that properly validates the secure_key authorization. No workarounds are available.
8.1.6
- Create a complete backup of the PrestaShop 8.1.5 database and all files
- Place the PrestaShop site in maintenance mode to prevent user access during upgrade
- Download PrestaShop version 8.1.6 from the official source (prestashop.com/project)
- Upload the PrestaShop 8.1.6 files to your server, replacing the existing 8.1.5 installation
- Run the PrestaShop upgrade process or execute composer install if using Composer-based installation
- Clear all PrestaShop caches (var/cache/, var/logs/ and admin directory caches)
- Verify that the secure_key parameter vulnerability is fixed by attempting to access an invoice with a random key
- Test core functionality (checkout, payment processing, invoice generation, customer accounts)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prestashop
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34717 — 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-34717 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