M4 PdfPrestaShop extension · Prestashop
CVE-2022-45447
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 a directory traversal vulnerability. The “f” parameter is not properly checked in the resource /m4pdf/pdf.php, returning any file given its relative path. An attacker that exploits this vulnerability could download /etc/passwd from the server if the file exists.
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 confidenceThe M4 PDF plugin for Prestashop versions 3.2.3 and before contains a directory traversal vulnerability in /m4pdf/pdf.php. The 'f' parameter accepts file paths without proper validation, allowing attackers to use relative path sequences (e.g., ../../../etc/passwd) to read arbitrary files from the server filesystem.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 M4 PDF plugin installationLocate the M4 PDF plugin directory in the Prestashop modules folder (typically /modules/m4pdf/)Affected if The /modules/m4pdf/ directory exists on the server
-
Check M4 PDF plugin versionInspect the version in the config.xml or main PHP file of the M4 PDF plugin, typically found in /modules/m4pdf/config.xml or within the main plugin PHP fileAffected if The installed version is 3.2.3 or any earlier version (versions higher than 3.2.3 are not affected)
-
Confirm vulnerable endpoint existsCheck for the existence of /m4pdf/pdf.php file within the plugin directoryAffected if The file /modules/m4pdf/m4pdf/pdf.php exists (path may vary based on plugin structure)
-
Test for directory traversal vulnerabilitySend a request to the pdf.php endpoint with a manipulated 'f' parameter containing directory traversal sequences (e.g., ?f=../../../config/settings.inc.php)Affected if The server returns file contents from outside the intended directory, confirming the vulnerability is exploitable
If the M4 PDF plugin version is 3.2.3 or lower and the vulnerable pdf.php endpoint is accessible, the environment is affected by this directory traversal vulnerability.
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 dataImplement strict input validation on the 'f' parameter to block directory traversal sequences ('..') and verify the resolved file path remains within an allowed directory. Alternatively, upgrade to a patched version of the M4 PDF plugin if available.
Fix this in M4 Pdf
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45447 — 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-45447 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