dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-45385

HIGH · 7.5 CVSS v3.1 Published 2024-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
ProQuality pqprintshippinglabels before v.4.15.0 is vulnerable to Directory Traversal via the pqprintshippinglabels module.

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 confidence

The pqprintshippinglabels module before version 4.15.0 is vulnerable to directory traversal, allowing attackers to access files outside the intended directory by manipulating file path inputs with sequences like '../'. This can lead to unauthorized disclosure of sensitive system files.

MitigationUpgrade pqprintshippinglabels to version 4.15.0 or later. Additionally, implement strict input validation and canonicalization of file paths to prevent traversal sequences.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify pqprintshippinglabels module version
    Locate the module's version file or header comment. Common locations include module configuration files, composer.json, or the main module PHP file where version is typically declared.
    Affected if The installed version is any version prior to 4.15.0 (e.g., 4.14.x, 4.13.x, etc.)
  2. Confirm the module is installed and active
    Check if pqprintshippinglabels appears in the system's list of installed modules and verify its current status (enabled/disabled) through the platform's admin interface or module database table.
    Affected if The module is installed AND active in the system, making the vulnerable code reachable.
  3. Examine module file handling code
    Inspect the pqprintshippinglabels module source code for functions that accept file path parameters or perform file operations. Look for any code paths that process user-supplied input as file paths without proper sanitization.
    Affected if The module contains file operation code that processes user input without validating or normalizing path sequences.
  4. Check for web server access logs
    Review web server access logs for the module's endpoints, searching for requests containing '../' path traversal sequences directed at the pqprintshippinglabels module.

You are affected if pqprintshippinglabels module version is below 4.15.0 and the module is currently enabled, as the directory traversal vulnerability exists in unpatched versions of this module.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade pqprintshippinglabels to version 4.15.0 or later. Additionally, implement strict input validation and canonicalization of file paths to prevent traversal sequences.

Recommended fix High confidence

pqprintshippinglabels v4.15.0

  1. Log in to the PrestaShop back office and locate the pqprintshippinglabels module in Modules > Modules & Services.
  2. Check the currently installed version; if it is lower than 4.15.0 the installation is vulnerable.
  3. Back up the entire PrestaShop file tree and the associated database.
  4. Download the latest module package (version 4.15.0) from the official PrestaShop Addons marketplace or from ProQuality’s support site.
  5. In the back office, use the module’s “Upgrade” button, or uninstall the old version and then install the newly downloaded version.
  6. After installation, clear the PrestaShop cache (Advanced Parameters > Performance > Clear cache).
  7. Verify the fix by generating a test shipping label and confirming that the directory‑traversal vulnerability is no longer exploitable.
  8. Review the module’s changelog or release notes to ensure any new configuration options are applied if needed.
Caveat No major breaking changes reported; minor configuration adjustments may be required.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45385 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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