PrestashopCMS
CVE-2026-33674
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 improperly use the validation framework. 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 · moderate confidencePrestaShop versions prior to 8.2.5 and 9.1.0 contain a vulnerability due to improper use of the validation framework, which could allow attackers to bypass input validation checks. The vulnerability has a medium severity (CVSS 5.3) and requires upgrading to one of the fixed versions.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Locate PrestaShop installation versionCheck the version.php file in the app/ directory or access the PrestaShop admin dashboard and navigate to Advanced Parameters > Configuration Information to view the installed versionAffected if Version displayed is lower than 8.2.5 or falls between 9.0.0 and 9.1.0 (exclusive)
-
Verify exact version numberIf using the admin panel, the exact version number is shown in the first line of the Configuration Information page; if using CLI, check the file ps_root_dir/composer.json for the 'version' fieldAffected if The version shown is any release prior to 8.2.5, or any 9.0.x release below 9.1.0
Your PrestaShop installation is affected if the installed version is less than 8.2.5, or is version 9.0.0 through 9.0.x (any 9.0.x version below 9.1.0).
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 to address the improper validation framework usage. No workarounds are available.
Upgrade to PrestaShop 8.2.5 (if on 8.x branch) or 9.1.0 (if on 9.x branch)
- 1. Back up your entire PrestaShop installation and database before proceeding
- 2. Download the appropriate fixed version (8.2.5 or 9.1.0) from the official PrestaShop releases
- 3. If upgrading from 8.x to 8.2.5: Upload the 8.2.5 files to your server, overwriting existing files while preserving your config/settings files
- 4. If upgrading from 9.0.x to 9.1.0: Upload the 9.1.0 files to your server, overwriting existing files while preserving your config/settings files
- 5. Clear all cache directories (var/cache, var/app/cache)
- 6. Verify the installation by logging into the admin panel
- 7. Test core functionality (catalog, cart, checkout, payment)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prestashop
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33674 — 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-33674 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