M4 PdfPrestaShop extension · Prestashop
CVE-2022-45448
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 · uneditedM4 PDF plugin for Prestashop sites, in its 3.2.3 version and before, is vulnerable to an arbitrary HTML Document crafting vulnerability. The resource /m4pdf/pdf.php uses templates to dynamically create documents. In the case that the template does not exist, the application will return a fixed document with a message in mpdf format. An attacker could exploit this vulnerability by inputting a valid HTML/CSS document as the value of the parameter.
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 confidenceThe M4 PDF plugin for PrestaShop (versions 3.2.3 and prior) contains an arbitrary HTML document crafting vulnerability in /m4pdf/pdf.php. When a requested template does not exist, the application returns a fixed document with an mpdf-formatted message. An unauthenticated attacker can exploit this by providing arbitrary HTML/CSS content as a parameter value, potentially enabling XSS or PDF content manipulation.
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
M4 PdfPrestaShop extension
<= 3.2.3CVSS 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.
-
Confirm M4 PDF plugin is installedCheck for the presence of the m4pdf directory in the PrestaShop modules folder (typically /modules/m4pdf/)Affected if The m4pdf directory exists in the modules folder
-
Identify installed M4 PDF versionLook for a version file or check the main PHP file within the m4pdf module directory for a version definitionAffected if The installed version is 3.2.3 or any version prior to 3.2.3
-
Verify vulnerable endpoint existsConfirm that the file /m4pdf/pdf.php exists in the PrestaShop installationAffected if The file /m4pdf/pdf.php is present and accessible via web
-
Test for template parameter injectionSend an HTTP request to /m4pdf/pdf.php with a non-existent template name (e.g., ?template=nonExistentTemplate) and include HTML/CSS in an additional parameterAffected if The response returns an mpdf-formatted document containing the arbitrary HTML/CSS content provided in the request parameters
The environment is affected if the M4 PDF plugin version is 3.2.3 or lower and the /m4pdf/pdf.php endpoint returns user-supplied HTML/CSS content in its error document when a template is not found.
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.
From vendor dataUpdate to a patched version of the M4 PDF plugin if available; otherwise, implement strict input validation and sanitization on all parameters passed to the PDF generation endpoint, and enforce proper template existence checks before processing.
Fix this in M4 Pdf
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45448 — 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-2022-45448 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