CVE-2024-34991
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 · uneditedIn the module "Axepta" (axepta) before 1.3.4 from Quadra Informatique for PrestaShop, a guest can download partial credit card information (expiry date) / postal address / email / etc. without restriction due to a lack of permissions control.
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 Axepta module for PrestaShop before version 1.3.4 contains an Insecure Direct Object Reference (IDOR) vulnerability allowing unauthenticated guest users to access sensitive customer data including partial credit card information (expiry dates), postal addresses, and email addresses without any permission checks.
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 Axepta module is installedLocate the Axepta payment module in your PrestaShop installation directory (typically in modules/axepta or similar) and confirm it existsAffected if The Axepta module directory exists in your PrestaShop modules folder
-
Determine installed Axepta module versionOpen the main PHP file of the Axepta module and look for a version definition (often in a variable like $this->version or within module metadata), or check the module's configuration page in the PrestaShop back office for the version numberAffected if The installed version is below 1.3.4 (e.g., 1.3.3, 1.3.2, etc.)
-
Confirm guest checkout is enabledIn PrestaShop back office, navigate to Shop Parameters > Customer Settings and verify if guest checkout option is enabled, or check the configuration file for guest checkout permissionsAffected if Guest checkout is allowed without requiring customer authentication
-
Review access logs for unauthorized data accessExamine your web server access logs and PrestaShop debug logs for unusual or批量 requests to Axepta module endpoints that retrieve customer order data, postal addresses, or payment information without valid authentication tokensAffected if Logs show requests to Axepta module data endpoints from unauthenticated IP addresses, especially if occurring frequently or in unusual patterns
You are affected if the Axepta module version is below 1.3.4 AND guest checkout is enabled, allowing unauthenticated access to customer data through the vulnerable IDOR endpoint.
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.
dbcve · scopedUpdate the Axepta module to version 1.3.4 or later immediately. Review access logs to determine if unauthorized data exfiltration has occurred and notify affected customers as required by regulations.
Upgrade Axepta module to version 1.3.4
- Log in to the PrestaShop Back Office.
- Navigate to the 'Modules' > 'Module Manager' section.
- Locate the 'Axepta' (axepta) module in the list of installed modules.
- Check the current version. If version 1.3.4 or later is available in the PrestaShop Addons catalog, click the 'Update' button next to the module.
- If the fixed version is not available in the catalog, download version 1.3.4 (or the latest available version) directly from the vendor (Quadra Informatique).
- Uninstall the existing vulnerable version of the module.
- Upload and install the new version (1.3.4 or later) via the 'Upload a module' button or by reinstalling the zip file.
- Clear the PrestaShop cache (under Advanced Parameters > Performance) to ensure the new code is loaded.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34991 — 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-2024-34991 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