PrestashopCMS
CVE-2024-34716
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. A cross-site scripting (XSS) vulnerability that only affects PrestaShops with customer-thread feature flag enabled is present starting from PrestaShop 8.1.0 and prior to PrestaShop 8.1.6. When the customer thread feature flag is enabled through the front-office contact form, a hacker can upload a malicious file containing an XSS that will be executed when an admin opens the attached file in back office. The script injected can access the session and the security token, which allows it to perform any authenticated action in the scope of the administrator's right. This vulnerability is patched in 8.1.6. A workaround is to disable the customer-thread feature-flag.
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 confidenceA stored XSS vulnerability in PrestaShop 8.1.0-8.1.5 allows attackers to inject malicious scripts via file attachments uploaded through the front-office contact form when the customer-thread feature flag is enabled. The XSS executes when administrators view the attachment in the back office, enabling session hijacking and unauthorized authenticated actions.
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.0, < 8.1.6CVSS 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.
-
Verify PrestaShop version is in affected rangeLocate the version file or admin panel to confirm the installed PrestaShop version. Common locations include the changelog file, the About section in the back office, or the config file. Compare against the affected range 8.1.0 to 8.1.5.Affected if The installed version is >= 8.1.0 and < 8.1.6
-
Confirm customer-thread feature flag statusAccess the PrestaShop back office and navigate to the Advanced Parameters > Configuration page, or inspect the configuration database table (typically ps_configuration) for the PS_CUSTOMER_THREAD feature flag setting. Determine if it is enabled.Affected if The customer-thread feature flag is enabled (value set to 1) in the configuration
-
Check if contact form file attachments are allowedNavigate to the front-office contact form configuration in the back office (usually under Customer Service > Customer Service Settings or similar). Verify whether the option to allow file attachments is enabled.Affected if File attachments are permitted on the front-office contact form
-
Inspect back office for customer threads with attachmentsIn the back office, go to the Customer Service section and review any customer threads or contact form submissions that include file attachments uploaded from the front office.Affected if There are customer threads with file attachments visible in the back office that originated from the front-office contact form
You are affected if your PrestaShop version is between 8.1.0 and 8.1.5 AND the customer-thread feature flag is enabled AND file attachments on the contact form are allowed, as the attack requires all three conditions to be exploitable.
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 · scoped8.1.6
Upgrade to PrestaShop 8.1.6 or later to apply the security patch, or disable the customer-thread feature flag as a workaround if upgrading is not immediately feasible.
8.1.6
- Ensure you have a complete backup of your PrestaShop installation and database before proceeding
- Download PrestaShop version 8.1.6 from the official PrestaShop website or GitHub releases
- Upload the new files to your server, overwriting the existing installation
- Run any available database migrations or upgrade scripts if included in the release
- Verify the upgrade was successful by logging into both the front-office and back-office
- Alternatively, as a mitigation, disable the customer-thread feature-flag in your PrestaShop configuration to prevent exploitation until you can upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prestashop
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34716 — 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-34716 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