CVE-2023-50029
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 · uneditedPHP Injection vulnerability in the module "M4 PDF Extensions" (m4pdf) up to version 3.3.2 from PrestaAddons for PrestaShop allows attackers to run arbitrary code via the M4PDF::saveTemplate() method.
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 PHP code injection vulnerability exists in the M4PDF::saveTemplate() method of the m4pdf PrestaShop module (versions up to 3.3.2 from PrestaAddons), allowing remote attackers to inject and execute arbitrary PHP code on the server via unsanitized input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 m4pdf module installationCheck if the m4pdf module directory exists in the PrestaShop modules folder (typically /modules/m4pdf/)Affected if The m4pdf directory does not exist in the modules folder - not affected
-
Identify installed m4pdf versionOpen the main m4pdf module file (usually m4pdf.php) and locate the version definition, typically in a variable like $this->version or the module's config XMLAffected if Installed version is 3.3.2 or earlier (any version up to and including 3.3.2)
-
Check if saveTemplate method is accessibleExamine the m4pdf.php file for the saveTemplate() method and determine if it is exposed through a front controller or admin controller action without authentication checksAffected if The saveTemplate method is reachable via a public or admin URL without proper sanitization of input parameters
-
Inspect input handling in saveTemplate methodReview the saveTemplate() function code for use of unsanitized user input (such as $_POST, $_GET, or request parameters) passed to eval(), file_put_contents(), or similar PHP functions that execute codeAffected if The method uses unsanitized input with code execution functions (eval, file_put_contents with dynamic paths, etc.) and version is <= 3.3.2
A user is affected if the m4pdf module is installed with version 3.3.2 or earlier and the saveTemplate method processes unsanitized input.
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 · scopedUpdate the m4pdf module to version 3.3.3 or later to receive the patched version, or remove the module entirely if not required for operations.
M4 PDF Extensions (m4pdf) module version > 3.3.2 from PrestaAddons
- Identify the current installed version of the M4 PDF Extensions (m4pdf) module in your PrestaShop installation
- Contact PrestaAddons to obtain the latest fixed version of the module (version higher than 3.3.2)
- Before upgrading, perform a complete backup of your PrestaShop database and files
- Test the upgrade in a staging environment before deploying to production
- Upgrade the m4pdf module to the fixed version provided by PrestaAddons
- Verify the fix by checking that the M4PDF::saveTemplate() method no longer allows arbitrary PHP code execution
- Monitor system logs for any suspicious activity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50029 — 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-2023-50029 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