CVE-2026-39079
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 · uneditedAn issue in prestashop upsshipping all versions through at least 2.4.0 allows a remote attacker to obtain sensitive information via the /modules/upsshipping/logs/, and /modules/upsshipping/lib/UPSBaseApi.php components
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 PrestaShop upsshipping module (versions up to 2.4.0) contains an information disclosure vulnerability where the /modules/upsshipping/logs/ and /modules/upsshipping/lib/UPSBaseApi.php paths are directly accessible, potentially exposing sensitive log data or API credentials.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify upsshipping module is installedCheck if the /modules/upsshipping/ directory exists in the PrestaShop installation by inspecting the file system or listing installed modules via PrestaShop admin or database.Affected if The upsshipping module directory exists on the server.
-
Determine installed module versionCheck the module's version file (typically in the module's main directory, e.g., upsshipping.php or a config/version file) or look at the module information in PrestaShop's admin panel under Modules > Modules & Services.Affected if The installed version is 2.4.0 or lower.
-
Test exposure of logs directoryAttempt to access the URL /modules/upsshipping/logs/ directly via HTTP request (e.g., curl or browser) to see if directory listing is enabled and logs are exposed.Affected if The directory is accessible and displays log files.
-
Test exposure of API fileAttempt to access the URL /modules/upsshipping/lib/UPSBaseApi.php directly via HTTP request to see if the file is readable.Affected if The PHP file is accessible and its contents are displayed instead of being executed or blocked.
-
Inspect exposed files for sensitive dataIf the above paths are accessible, examine any visible log files or the API file to check for exposed credentials, API keys, or other sensitive information.Affected if Log files contain API credentials, tracking data, or other sensitive information, or the API file exposes configuration details.
If the upsshipping module is installed at version 2.4.0 or lower AND the /modules/upsshipping/logs/ or /modules/upsshipping/lib/UPSBaseApi.php paths are directly accessible via web, the environment is affected by this CVE.
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 dataRestrict web access to the upsshipping module directory, disable directory listing, and remove or secure exposed log files. Consider updating the module when a patch is released.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39079 — 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-2026-39079 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