PrestashopCMS
CVE-2026-33673
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. Versions prior to 8.2.5 and 9.1.0 are vulnerable to stored Cross-Site Scripting (stored XSS) vulnerabilities in the BO. An attacker who can inject data into the database, via limited back-office access or a previously existing vulnerability, can exploit unprotected variables in back-office templates. Versions 8.2.5 and 9.1.0 contain a fix. 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 versions prior to 8.2.5 and 9.1.0 contain a stored XSS vulnerability in back-office templates. An attacker with database injection capability (via limited BO access or another vulnerability) can inject malicious scripts through unprotected template variables that are not properly sanitized before rendering.
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.2.5>= 9.0.0, < 9.1.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check installed PrestaShop versionLook for a version.php or version.md file in the PrestaShop root directory, or check the admin dashboard footer for the version numberAffected if The version is less than 8.2.5 or is 9.0.0 through 9.0.x (prior to 9.1.0)
-
Verify back-office access controlsReview user accounts with back-office access in the admin panel under Team > Administrators or similar access management sectionAffected if Multiple users have back-office access or any account has limited BO access, creating potential for database injection capability
-
Inspect custom back-office templatesExamine any custom templates or modules in the /themes and /modules directories that override or extend BO templates for unsanitized template variablesAffected if Custom or third-party BO templates exist that may use unsanitized {$smarty} variables
-
Check for database injection indicatorsReview database logs or audit tables for unusual SQL patterns in fields that populate BO template variables, especially in product descriptions, CMS content, or configuration valuesAffected if Unexpected or malformed data is found in fields that are rendered in back-office templates without sanitization
-
Review admin activity logsExamine PrestaShop logs for any suspicious admin actions that could indicate exploitation attempts, particularly template-related operationsAffected if Unusual admin actions involving template variables or database modifications are logged
A user is affected if their PrestaShop installation runs version 8.2.5以下または9.0.0以上9.1.0未満 AND they have back-office users who could potentially inject malicious content into template-rendered fields.
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.2.59.1.0
Upgrade PrestaShop to version 8.2.5 or 9.1.0 or later to patch the XSS vulnerability in back-office templates.
Upgrade to PrestaShop 8.2.5 (for 8.x) or 9.1.0 (for 9.x)
- Create a complete backup of the PrestaShop database and files
- Determine the current PrestaShop major version (8.x or 9.x)
- Download the appropriate fixed version: 8.2.5 for 8.x branches or 9.1.0 for 9.x branches
- Follow the official PrestaShop upgrade documentation to apply the update
- Verify the upgrade was successful by logging into the back-office
- Test that the back-office templates properly encode user-supplied data
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prestashop
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33673 — 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-2026-33673 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