dbcve.org
MyinventoryPrestaShop extension · Webbax

CVE-2023-30197

HIGH · 7.5 CVSS v3.1 Published 2023-05-31
Fix available
A fix is available. Upgrade to 1.6.7 or later.
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
Incorrect Access Control in the module "My inventory" (myinventory) <= 1.6.6 from Webbax for PrestaShop, allows a guest to download personal information without restriction by performing a path traversal attack.

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 confidence

A path traversal vulnerability in the Myinventory module for PrestaShop (versions 1.6.6 and below) allows unauthenticated guests to access and download personal information by manipulating file paths in the inventory download feature. The module fails to properly validate or sanitize user-supplied path inputs, enabling directory traversal to access sensitive files outside the intended scope.

MitigationUpgrade the Myinventory module to version 1.6.7 or later which contains the security fix. If no update is available, implement input validation and path sanitization on all file access operations, and restrict the download functionality to authenticated users only.

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
MyinventoryPrestaShop extension
Affected:< 1.6.7

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. Confirm Myinventory module is installed
    Locate the Myinventory module directory in the PrestaShop installation, typically under modules/myinventory/ or modules/wbxmyinventory/. Check for the presence of the module folder and its main PHP files.
    Affected if The Myinventory module folder exists in the PrestaShop modules directory.
  2. Identify the installed module version
    Open the main module file (usually myinventory.php or wbxmyinventory.php) and locate the version property in the class definition, or check the module's config.xml file if present. Compare the version number against 1.6.7.
    Affected if The installed version is lower than 1.6.7 (e.g., 1.6.6, 1.6.5, etc.).
  3. Verify the inventory download feature is enabled
    Log into the PrestaShop admin panel and navigate to the Myinventory module configuration page. Check whether the download/inventory export functionality is enabled or accessible.
    Affected if The download feature is enabled and accessible from the front-end or admin panel.
  4. Test unauthenticated access to download function
    Attempt to access the inventory download endpoint directly without logging in. The vulnerable URL typically follows patterns like: /modules/myinventory/download.php?file=... or /modules/wbxmyinventory/controllers/front/download.php?filename=...
    Affected if The download function responds to unauthenticated (guest) requests without requiring login.

If the Myinventory module is installed with a version below 1.6.7 AND the download feature is accessible to unauthenticated users, the environment is affected by this path traversal vulnerability.

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
Upgrade available Upgrade to 1.6.7 or later
Fixed in 1.6.7
Interim mitigation

Upgrade the Myinventory module to version 1.6.7 or later which contains the security fix. If no update is available, implement input validation and path sanitization on all file access operations, and restrict the download functionality to authenticated users only.

Recommended fix High confidence

1.6.7

  1. Create a complete backup of your PrestaShop installation and database before making any changes
  2. Obtain the fixed version of the Myinventory module (version 1.6.7 or later) from a trusted source such as the official PrestaShop Addons marketplace or the vendor (Webbax)
  3. Navigate to your PrestaShop admin panel > Modules > Module Manager
  4. Locate the Myinventory module in the installed modules list
  5. Click on the upgrade button or uninstall the old version and install the fixed version 1.6.7
  6. Verify the module is running version 1.6.7 or later after installation
  7. Test that the path traversal vulnerability is no longer exploitable

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

Fix this in Myinventory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30197 — 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-30197 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