AI-assisted attacks: How do I protect my store and connected systems?
The new BSI assessment from a retailer’s perspective: what AI-assisted attacks mean for PrestaShop, Shopware, Shopify, ERP and advertising accounts.
- 1Direct answer
- 2Why the current security situation matters to your store
- 3How does AI change the exploitation of vulnerabilities?
- 4What should PrestaShop operators check?
- 5What differs with Shopware and Shopify?
- 6Why ERP systems and integrations belong in the security plan
- 7Can advertising accounts and marketing tools also be affected?
- 8What should retailers arrange now?
- 9A brief look at ransomware and internal IT
- 10Our assessment for online retail
- 11Sources & further reading
- 12About this article
Direct answer
The current security assessment gives retailers a reason to review their store, integrations and business accounts together. Security fixes need clear ownership and a reliable testing and deployment process. PrestaShop, Shopware and Shopify differ in how they are operated; access, ERP integrations and internal devices remain part of the responsibility in each case.
Why the current security situation matters to your store
An order arrives through the store, inventory comes from the ERP, and advertising brings the next visitor. Retailers experience this as one connected process. Security responsibilities, however, are often considered separately. That can leave a dangerous gap: someone maintains the store, but nobody checks an old integration or a former agency's advertising access.
This article responds to Heise's report of 19 November 2026 on the BSI's revised security assessment. We examine its implications for online retail. The platforms discussed illustrate different operating models. The report does not establish a single current attack campaign targeting PrestaShop, Shopware and Shopify together.
How does AI change the exploitation of vulnerabilities?
AI can reduce the work attackers need to do: examine reachable systems, assess indications of defects and assist with developing attack tools. Germany's BSI describes this development in its 2026 situation report. For operators, the implication is practical: a disclosed vulnerability can become an immediate concern sooner than a routine monthly maintenance schedule allows for.
The BSI's timing data illustrates the problem. For the second quarter of 2026, it reports an average of eight days between disclosure and the first known exploitation of a vulnerability. Across the entire current reporting period, the average was 25 days. Neither figure represents a safe waiting period for a store. The report covers July 2025 to June 2026; it is not simply a count of attacks during the past week.
Automation does not necessarily involve AI. Stolen credentials are also different from an exploited software defect. Both can harm a retailer, but they require partly different countermeasures. Updates cannot prevent every account takeover, and a second authentication factor cannot repair a vulnerable extension.
What should PrestaShop operators check?
For a self-hosted PrestaShop store, the application, modules, theme, server environment and integrations belong in the same inventory. An up-to-date core alone says little about whether an additional module is still maintained. A forgotten test installation containing real data also deserves attention.
We would first establish which versions are actually deployed, who follows vendor advisories and who is authorised to implement an urgent fix. The PrestaShop project's security policy makes clear that security fixes cannot be assumed for indefinitely old versions. Each advisory must be checked against the versions and extensions in use.
For our PrestaShop projects, sensible planning therefore includes a short route from an advisory to action: backup, targeted testing, deployment and verification of the affected functions. Where a vulnerability can be exploited immediately, restricting the affected functionality until a fix is available may also need consideration. Waiting for the next major relaunch is not a suitable maintenance plan.
What differs with Shopware and Shopify?
With Shopware, first establish the operating model. Businesses running their own installation need clear responsibilities for the platform, extensions and hosting. Shopware documents a Security Plugin for Shopware 6 that can deliver security fixes. Its suitability for the installed version and particular issue must be checked. It does not imply protection for every third-party plugin or the server environment.
With Shopify, Shopify operates the central platform. Merchants do not install patches on Shopify's servers themselves. That moves part of the technical work to the provider, but it does not remove the business's responsibility for users, apps, integrations and its own devices.
In practice, we would check who still has access to a Shopify store, which data its apps can reach and whether two-step authentication is configured. Unnecessary permissions should be removed. Independently operated custom apps or connected services still need a named owner. Cloud operation and complete protection are not the same thing.
Why ERP systems and integrations belong in the security plan
A connector may read orders, transfer customer records or change inventory. Its permissions should therefore follow its actual task. A product lookup does not automatically need write access to every business object. PrestaShop's documentation, for example, explains separately assignable webservice permissions. The API used depends on the version and integration.
For Odoo and other ERP systems, we also consider user roles, extensions and how the system is operated. Odoo's access-rights documentation distinguishes permissions for users and groups. An integration account should not receive the same extensive rights as an administrator merely for convenience.
As an Odoo partner, we do not consider an integration finished just because its first orders have transferred. Planning also needs to cover an accountable operator, understandable permissions and replacement of access keys. Those responsibilities must survive a change of service provider. Secrets belong in suitable protected storage, rather than openly accessible project documents; OWASP provides guidance on managing keys and credentials.
Can advertising accounts and marketing tools also be affected?
Yes. Depending on permissions, hijacked accounts can be abused to modify campaigns or spend advertising budgets. Google explicitly documents how to respond to a compromised Google Ads account, including checking users, manager accounts and payment profiles. This differs from a store vulnerability, but belongs in the same operational overview for a retailer.
We recommend including Google Ads, Meta advertising accounts, Merchant Center, Tag Manager and email marketing tools such as Klaviyo in access reviews. Who can publish, who can authorise spending, and which external partners remain connected? An up-to-date contact list is of limited use if the actual permissions do not match. Protecting the email accounts used to recover other accounts is particularly important.
For paid search and Google Ads, coordination should therefore extend beyond campaign objectives. Roles, approvals for sensitive changes and reviews of unusual spending also need discussion. A message claiming to come from support is not sufficient reason to disclose credentials or authentication codes.
What should retailers arrange now?
For an initial review, we at sjmedia would work through these six areas with the people responsible for the store, the hosting provider and internal IT:
- Inventory systems: assign an owner to the store, ERP, connectors, marketing tools, test environments and remote access.
- Prioritise fixes: match vendor advisories to deployed versions and handle urgent security updates separately from convenience features.
- Limit access: review former users and partners, use individual accounts and enable multifactor authentication wherever supported.
- Protect integrations: reduce permissions to the required scope and prepare controlled replacement of keys.
- Test recovery: verify protected backups, restoration and coordination between the store and inventory system.
- Define incident handling: agree reachable contacts, containment decisions and preservation of logs before an incident occurs.
This list does not replace an assessment of an actual system. It helps turn a general warning into tasks that can be checked. A suspected ongoing attack requires qualified incident-response specialists; a routine store update alone does not clean a compromised system.
For a practical inventory, see our companion guide: How do I check the security of my online store? It sets out concrete checks and explains assessment, maintenance, Security and Protect.
A brief look at ransomware and internal IT
A reachable storefront can still be commercially paralysed if the business behind it cannot process orders. Encrypted ERP data or unavailable shipping workstations can block fulfilment while customers continue buying. Internal computers, remote maintenance, network separation and backups therefore belong in the assessment.
The ransomware guide from CISA and partner agencies covers protected, separated backups and prepared responses, among other measures. Restoration needs to be tested in practice. A backup also does not undo data theft that has already occurred. At sjmedia, we focus on the store and integration side; retailers coordinate internal infrastructure with their IT team or a responsible security provider.
Our assessment for online retail
The current news should not trigger a rushed purchase of more security tools. Closing gaps in responsibility and being able to implement necessary work promptly matter more. A maintained PrestaShop installation, an appropriately operated Shopware system and a carefully managed Shopify store can each form part of a considered operating model. None automatically secures the connected accounts and processes.
We support businesses where store technology, extensions and integrations meet. The work required can only be scoped sensibly after reviewing the existing setup. A useful starting point is an honest answer to one question: who will notice a relevant security advisory, and who can then act on it?
Sources & further reading
- Heise: reporting on the BSI assessment, 19 November 2026
- BSI: 2026 security assessment
- BSI: full report and reporting periods
- PrestaShop: project security policy
- PrestaShop: webservice access permissions
- Shopware: security measures
- Shopify: protecting user sign-in
- Odoo: access rights
- OWASP: secrets management
- Google Ads: responding to account compromise
- CISA: ransomware preparation and response
About this article
Change log
21.11.2026First published.
Tags
Cite this article
Jochen Schmid (2026): AI-assisted attacks: How do I protect my store and connected systems? sjmedia GmbH, Kuppenheim. Reviewed by Johann Nehrlich. Updated 21.11.2026. https://www.sjmedia-consulting.de/en/blog-e-commerce/ki-angriffe-onlineshop-sicherheit





