dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-69633

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A SQL Injection vulnerability in the Advanced Popup Creator (advancedpopupcreator) module for PrestaShop 1.1.26 through 1.2.6 (Fixed in version 1.2.7) allows remote unauthenticated attackers to execute arbitrary SQL queries via the fromController parameter in the popup controller. The parameter is passed unsanitized to SQL queries in classes/AdvancedPopup.php (getPopups() and updateVisits() functions).

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 critical SQL injection vulnerability in the Advanced Popup Creator PrestaShop module (versions 1.1.26-1.2.6) allows remote unauthenticated attackers to execute arbitrary SQL commands via the unsanitized fromController parameter passed to the getPopups() and updateVisits() functions in classes/AdvancedPopup.php.

MitigationUpgrade the module to version 1.2.7 or later. As an interim measure, deploy WAF rules or request filtering to block SQL injection payloads in the fromController parameter until the patch can be applied.

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
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 checks

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

  1. Locate the Advanced Popup Creator module
    Check if the module directory exists in your PrestaShop installation under modules/ (common paths: modules/advancedpopupcreator, modules/advanced_popup_creator, or similar)
    Affected if The module directory exists and contains the Advanced Popup Creator files
  2. Identify the module version
    Open the module's main PHP file or config.xml and look for a version declaration (often in a $this->version variable or <version> tag)
    Affected if The installed version falls within 1.1.26 through 1.2.6 (inclusive)
  3. Verify the vulnerable file exists
    Confirm the presence of classes/AdvancedPopup.php within the module directory
    Affected if The file exists and contains the getPopups() and updateVisits() functions
  4. Check if the module is enabled
    In the PrestaShop admin panel, navigate to Modules > Module Manager and verify the Advanced Popup Creator status, or query the ps_module database table for the module's active status
    Affected if The module is installed and enabled (active)
  5. Confirm the fromController parameter handling
    Inspect the getPopups() and updateVisits() functions in classes/AdvancedPopup.php for direct use of the fromController request parameter in SQL queries without sanitization
    Affected if The code directly passes $_POST['fromController'] or similar unsanitized input into SQL queries

You are affected if the Advanced Popup Creator module is installed with a version between 1.1.26 and 1.2.6, the vulnerable file exists, and the module is enabled with unsanitized fromController parameter usage in the codebase.

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 the module to version 1.2.7 or later. As an interim measure, deploy WAF rules or request filtering to block SQL injection payloads in the fromController parameter until the patch can be applied.

Recommended fix High confidence

1.2.7

  1. 1. Identify the Advanced Popup Creator module installation directory in your PrestaShop modules folder
  2. 2. Download the latest version 1.2.7 or later of the Advanced Popup Creator module from the official source (addons.prestashop.com)
  3. 3. Backup your current module installation and database before proceeding
  4. 4. Upload and install the updated module version 1.2.7
  5. 5. Clear the PrestaShop cache (var/cache/ or via admin panel)
  6. 6. Verify the fix by confirming the fromController parameter is now properly sanitized in classes/AdvancedPopup.php (getPopups and updateVisits functions)
Caveat Module updates may have minor template or feature changes; test in staging environment before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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