Abandoned Cart Reminder ProPrestaShop extension · Prestashop
CVE-2024-28392
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 · uneditedSQL injection vulnerability in pscartabandonmentpro v.2.0.11 and before allows a remote attacker to escalate privileges via the pscartabandonmentproFrontCAPUnsubscribeJobModuleFrontController::setEmailVisualized() method.
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 confidenceA SQL injection vulnerability exists in the PrestaShop module pscartabandonmentpro (versions 2.0.11 and prior). The flaw resides in the setEmailVisualized() method of the front controller, where user-supplied input is not properly sanitized before being used in SQL queries. This allows remote unauthenticated attackers to inject arbitrary SQL statements, potentially escalating privileges by manipulating database records or gaining administrative access.
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
Abandoned Cart Reminder ProPrestaShop extension
<= 2.0.11CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate the pscartabandonmentpro module installationSearch for the pscartabandonmentpro module directory in your PrestaShop modules folder (typically /modules/pscartabandonmentpro) or use the PrestaShop back-office Modules section to list installed modulesAffected if The module directory or entry exists in your PrestaShop installation
-
Identify the installed module versionCheck the module's main PHP file for a version constant or inspect the module's info.xml/config.xml file for the version numberAffected if The version number found is 2.0.11 or lower
-
Verify the vulnerable front controller existsLocate the front controller file within the pscartabandonmentpro module directory and search for the setEmailVisualized() method definitionAffected if The method contains unsanitized SQL query construction using user-supplied input
-
Confirm the module is enabled and accessibleCheck through PrestaShop back-office that pscartabandonmentpro is installed and enabled, and verify the front controller endpoint is reachable via the webAffected if The module is active and its front controller URL is publicly accessible without authentication
You are affected if pscartabandonmentpro version 2.0.11 or lower is installed and enabled, with the vulnerable setEmailVisualized() method present in an accessible front controller.
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 · scopedUpgrade pscartabandonmentpro to a patched version that properly sanitizes SQL inputs, or implement parameterized queries in the setEmailVisualized() method to prevent injection.
Version 2.0.12 or later (if available on PrestaShop Addons)
- Check addons.prestashop.com for the latest version of Abandoned Cart Reminder Pro (pscartabandonmentpro)
- If version 2.0.12 or higher is available, upgrade to it to remediate the SQL injection vulnerability
- After upgrade, verify the setEmailVisualized() method no longer accepts unsanitized user input
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Abandoned Cart Reminder Pro
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28392 — 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-28392 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