Sin impuesto Con impuesto

Third-party modules: how to assess whether a module is safe before installing it

Every module you install is code that runs in your store with full permissions. These questions help you decide whether it is worth it.

Jesús Meilán
Updated: 26/09/2026 114
Third-party modules: how to assess whether a module is safe before installing it
Share:

Most serious vulnerabilities in PrestaShop stores are not in the core, but in modules. The point is not to install none, but to choose well.

Before buying or downloading

  • Source: PrestaShop Addons or the developer’s website. Never “free” versions of paid modules: they usually come with a gift attached.
  • Updates: when was the last one? Does it support your PrestaShop and PHP versions?
  • Support: does the developer respond? Is there a changelog?

When reviewing the package

  • Overrides: how many does it install? Each one is a source of future conflicts.
  • Public entry points: standalone PHP files accessible from outside (ajax.php, cron.php, export.php) without a token check are the most common vulnerability.
  • SQL queries with unescaped variables (pSQL(), (int)).
  • Obfuscated code: a module that hides its code does not let you know what it does.
  • Calls to external servers: what data does it send, and where?

After installing

  • Test it first on a copy of the store.
  • Check which hooks it registers and on which pages it acts.
  • If it stops being used, uninstall it and delete its folder.
A specific warning sign: a module that compares its endpoint token with a configuration key that does not exist. Comparing against an empty value can let anyone through. We have seen it in export and migration modules.
Loading...
Cookie consent
Back to top