
A customer uses your contact form to ask where her order is. Your support agent opens the message in the back office, replies in two lines and moves on. In those few seconds, a program hidden in the message has taken over her session. Nobody clicked anything.
This scenario has a name: the PrestaShop vulnerability CVE-2026-44212, rated 9.3 out of 10. The fix has been available since April 28, 2026, and we applied it in April and May on every PrestaShop store we maintain. But many stores with no maintenance plan still run old versions, and a ready-to-use exploit has been circulating publicly since November 11. Several of those stores reached out to us after being hacked, and we analyzed the incident piece by piece, from the public form to the backdoor planted on the server.
This guide explains the vulnerability in plain English, walks through the attack as we observed it, and shows you how to check your store, fix it and find out whether someone already got in. It ends with the PrestaShop security practices that keep the next vulnerability from turning into the same story, and answers a question many merchants ask: is PrestaShop secure?
At a glance
CVE-2026-44212 is a stored XSS (cross-site scripting) vulnerability in the PrestaShop back office. An attacker saves a piece of code in your database; it sits there quietly, then runs in the browser of whoever displays the page that contains it. Here, that page is a customer message, under Customers > Customer Service.
Three things make it especially dangerous. No access is needed: the contact form is public. The victim is the most powerful person in the store, the owner, the customer service manager or an administrator, and the code runs with their permissions. And nothing looks wrong: the message reads like an ordinary request.
PrestaShop sums up the impact as session hijacking and full back-office takeover. With an administrator account, that means being able to install a module, in other words to run arbitrary code on the server.
The flaw was responsibly disclosed to PrestaShop by Savio, a researcher at Doyensec, in collaboration with Anthropic Research. The PrestaShop maintainers shipped the fix on April 28, 2026, then published the detailed security advisory (GHSA-w9f3-qc75-qgx9) on May 8. The CVE number went public on May 14, 2026.
There is no big design flaw here, just two details that open the door when combined:
Most published analyses stop at “session hijacking is possible”. In the field, the attack goes much further. When hacked stores with no maintenance plan asked us for help, our system administrator analyzed the incident and rebuilt the whole chain from a real booby-trapped message, its payload decoded without running it, and the code of the store involved, a PrestaShop 1.7.8.11. The diagram below sums it up in five stages.

The table below details the eight steps, side by side: what the attacker does and what your team sees. The right-hand column is the unsettling one.
| Step | What the attacker does | What your team sees |
|---|---|---|
| 1. Submission | Fills in the contact form: the trap in the email field, a large encoded program (about 128 KB) in the message field. | Nothing. The form says “Message sent”. |
| 2. Validation | The booby-trapped address complies with the email standard: PrestaShop accepts it. | Nothing. |
| 3. Storage | The message and the address are saved as is in the database. | A new message in Customer Service. |
| 4. Display | In the back office, the address is inserted into the page unescaped: the trap becomes live code. | The message page looks normal. |
| 5. Trigger | A recent browser feature runs the code as soon as the page loads, with no click. | Nothing: opening the message is enough. |
| 6. Reconnaissance | The program reads the back-office menu to learn the employee’s permissions, then swaps the suspicious content for a fake customer message. | A routine request from a customer waiting for her order. |
| 7. Action | If permissions allow, it installs a malicious module and tries to erase its tracks. If not, the trap stays in place for the next employee. | Nothing. That is why we still found booby-trapped messages. |
| 8. Backdoor | The module edits a configuration file so it reloads on every visit, ships the database and credentials out, adds more entry points and fakes file dates. | The store runs normally. |
Three details show how well prepared the attackers were. The trap fits entirely within allowed characters: anything that could have been blocked is turned into strings of numbers. The trigger relies on an event that modern browsers have all supported since 2024 and that fires on its own when the page renders; many security filters, which look for the usual XSS keywords, do not know it.
The third detail is the sneakiest. The fake customer message replaces the suspicious content on screen, so the employee notices nothing. And when the employee’s permissions are too limited, the attacker simply waits: the trap stays in the database for the next, more powerful account.
Once the backdoor is in place, the attacker controls the store like its technical administrator. In the cases we analyzed, it exfiltrated the configuration file (database credentials and the store’s security keys) and the full database: customers, addresses, order history, employee accounts.
With that level of access, nothing stops it from tampering with checkout pages to steal card numbers, as in the digital skimming campaigns PrestaShop has warned about before, or from selling the access to someone else.
According to PrestaShop, the vulnerability affects every version before 8.2.6 and, on the 9.x branch, versions 9.0.0 to 9.1.0. Our own review confirms that older branches, 1.5 through 1.7, share the same flaw. Since the contact form module ships by default, almost every store is exposed.
| PrestaShop version | CVE-2026-44212 | Our recommendation |
|---|---|---|
| 9.1.1 and later (9.2.1 recommended) | Fixed | Check older messages and stay up to date. |
| 9.0.0 to 9.1.0 | Vulnerable | Update to the latest 9.x release right away. |
| 8.2.6 and later (8.2.9 recommended) | Fixed | Stay up to date and plan the move to 9.x: the 8.2 branch now only gets security fixes. |
| 8.0.0 to 8.2.5 | Vulnerable | Update to 8.2.9, or install the hotfix module in the meantime. |
| 1.7.x | Vulnerable | Install the official hotfix module now, then plan a migration. |
| 1.6.x and 1.5.x | Vulnerable | Manual fix by a developer right away, then migration: no official patch. |
These branches are still common even though they are no longer maintained. No new release comes out for them: short of upgrading, the only protection is the official hotfix module for 1.7, or a manual fix for 1.6. Our advice is blunt: this PrestaShop vulnerability is the right moment to migrate your store to a supported version. Staying on an abandoned branch means waiting for the next flaw with no patch coming.
Start by finding your exact PrestaShop version. It appears in the back office under Advanced Parameters > Information, and often at the bottom of the back-office login page. Write down the full number, with its three or four parts (for example 1.7.8.11 or 8.2.5).
Two situations deserve a check even if you are up to date. First, a store that was updated recently: if it stayed vulnerable for months, a booby-trapped message may have been opened before the update, and the fix does not remove a backdoor already in place. Second, a customized back office: the fix changes specific files, and if a developer replaced those files with custom versions, the protection may not apply.
Not sure which version your store runs, or whether the fix is really applied? Ask for a free check of your store
PrestaShop offers three ways to get protected. They differ in cost and in scope.
| Option | For whom | Pros | Limits |
|---|---|---|---|
| Update PrestaShop (8.2.9 or 9.2.1) | Stores on 8.x or 9.x | Safest Also fixes every other known flaw. | Requires a backup and testing (modules, theme, checkout). |
| Official hotfix module | Stores on 1.7, 8.x and 9.x that cannot update right away | Fast Backs up the faulty file, then applies the fix. | Only covers this flaw: the update still needs planning. |
| Manual fix | Stores on 1.6 or older, customized back offices | Works everywhere, even with no official patch. | Developer needed One mistake can break the back office. |
A PrestaShop update fixes CVE-2026-44212 and every flaw patched since your version. For a store on 8.x, moving to 8.2.9 stays on the same branch and usually needs no rebuild. For a store on 1.7, moving to 8.x or 9.x is a real migration: modules and theme must be checked, sometimes replaced. On a store that sells, we recommend testing the new version on a copy of the site before applying it to production; our guide to installing PrestaShop 9 shows the steps for a clean staging copy.
PrestaShop publishes a free module, pshotfix_ghsaw9f3qc75qgx9, compatible with versions 1.7, 8.x and 9.x. It installs like any other module (Modules > Module Manager > Upload a module), backs up the vulnerable file and applies the fix automatically. Download it only from PrestaShop’s official repository, never from a third-party site: a fake patch would be the perfect Trojan horse.
{admin_folder}/themes/default/template/controllers/customer_threads/helpers/view/view.tpl, replace each {$thread->email} with {$thread->email|escape:'html':'UTF-8'}. On older branches, the same flaw exists in customer_threads/message.tpl and is fixed the same way. Then clear the Smarty cache.classes/Validate.php, switch the isEmail() method to strict mode, which rejects quoted addresses.While you wait for the update, and afterwards too, three measures cut the risk sharply. A web application firewall (WAF) can block contact form submissions whose email starts with a quote or contains spaces: no real address looks like that. Employee accounts should have limited permissions, because the person handling customer service has no reason to install modules; the weaker the account, the shorter the attack goes. Finally, a dedicated browser for the back office, with no unnecessary extensions, limits the damage of a hijacked session.
No developer at hand to apply the fix safely? Have our team apply the fix within 48 hours
Fixing the PrestaShop vulnerability closes the door. It does not tell you whether someone already walked in. Some checks are within your reach in the back office; others need a technician on the server.
The mockup below shows a Customer Service inbox on a fictional store. The second message shows the typical signs of a booby-trapped one.
" [email protected] ……… (very long text) ……… x="@x.xx="@x.x: no real address looks like this.Beyond messages, review your module list: a module you never installed, often with a name that imitates PrestaShop’s own, should raise a flag. Do the same for employees and Webservice access: an account or API key created recently, for no known reason, is suspicious.
On the server side, a technician will look for:
For a developer, a simple query on the ps_customer_thread table lists email addresses that start with a quote or contain a space. In normal traffic there are virtually none.
Our guide website hacked? what to do now walks through the cleanup method step by step.
Suspicious signs in your back office? Have our security team inspect and clean your store
When a backdoor ships your database out, the problem becomes a legal one. Names, email and mailing addresses, order history: this is personal information, and the law expects you to act fast.
Keep a log from day one of what you find and what you do: you will need it for notifications, for your insurer and for any police report. This information is general; if a breach is confirmed, get advice from your lawyer or privacy officer.
CVE-2026-44212 hits the PrestaShop core, but it is not typical of most hacks. Experts across the ecosystem keep saying it: most intrusions come through third-party modules that are free, abandoned or downloaded outside official channels. A well-protected store rests on a few simple habits.
Every installed module is extra code that may contain a flaw. Keep the list as short as possible, remove unused modules (disabling them is not always enough) and favor modules their vendor still maintains. The Friends of Presta collective publishes a public registry of PrestaShop module vulnerabilities: checking it before installing a module, then regularly, is a good habit.
A PrestaShop security module can add a firewall, watch files or limit login attempts. That is useful, but it does not replace updates: no module would have stopped the backdoor once an administrator session was hijacked. We advise against stacking several security modules, which get in each other’s way and slow the store down.
The randomly named admin folder that PrestaShop creates at install time should stay that way. Add a layer in front of it (IP restriction or extra authentication at the server level or through a service like Cloudflare), unique passwords, and one named account per employee with only the permissions they need.
PrestaShop, its modules and theme, but also PHP and the server: a flaw can come from any layer. The PHP2Shell vulnerability of October 2026 proved it, since it hit the language itself rather than the CMS; our guide to the PHP2Shell vulnerability and PHP updates explains how to check that layer.
Daily database backups and weekly file backups, stored off the server and tested, let you restart from a clean version. File monitoring flags any unexpected change, which would have exposed the backdoor the moment it was planted. For a complete review, our website security guide lists the checks worth running before an incident.
Yes, as long as it is maintained. PrestaShop has a public security policy, publishes advisories and ships fixes quickly, as this case shows: the patch, a hotfix module and a manual procedure all came out the same day. The weak point is rarely the software itself; it is the time between a fix and its installation, and the pile of unmaintained modules. A store kept up to date by someone who follows the advisories is as safe as any other e-commerce platform. A store left on 1.6 or 1.7 with no follow-up is not.
Merchants think about protecting checkout and passwords, rarely the contact form. Yet anything a visitor can type on your site (contact form, reviews, order fields) ends up displayed somewhere, often in the back office. Our website security analysis of a suspicious traffic spike shows how often forms are probed.
The fix dates from April, the attacks from November. The hacked stores we analyzed all had one thing in common: none had applied the April fix, because nobody was keeping track. They were not hit by an unknown flaw, but by an update that never happened. That is the most common case: attackers rarely exploit secret flaws, they exploit delays.
Card fraud, a leaked customer file, being blocked by Google or by your payment provider, cleanup costs: a compromised store costs far more than regular maintenance. And customer trust cannot be restored from a backup.

That is exactly what made the difference: on the stores we maintain, the PrestaShop vulnerability CVE-2026-44212 was fixed in April and May 2026, well before the wave of attacks. A serious website maintenance agreement covers security monitoring for PrestaShop, its modules and the server, fast patching after testing on a copy of the store, verified off-site backups, file monitoring and planned version upgrades, so you never get stuck on an abandoned branch.
At Aurone, our website maintenance services cover all of this for online stores in the United States, Canada and Europe. For stores still on 1.6 or 1.7, our migration services move them to PrestaShop 8 or 9 without interrupting sales. If you are weighing who should look after your store, read our comparison PrestaShop expert: freelancer or agency.
The PrestaShop vulnerability CVE-2026-44212 shows that a serious attack can fit in a simple contact message. It also shows that protection is within reach: an update, or a free module, closes the door. Between the stores that were hit and the others, the difference was neither size nor budget, but how long it took to apply a fix that had been available for months. Check your version today, and have your store inspected if it stayed vulnerable.
The PrestaShop vulnerability CVE-2026-44212 is a stored cross-site scripting flaw rated 9.3 out of 10. An attacker with no account hides malicious code in the email address of a message sent through the contact form. The code runs when an employee opens the message in the back-office Customer Service page, with that employee’s permissions. It allows a full back-office takeover and, with an administrator account, the installation of a malicious module.
Every PrestaShop version before 8.2.6 is affected, along with versions 9.0.0 to 9.1.0. That includes the 1.5, 1.6 and 1.7 branches, which are still widely used. Versions 8.2.6 and 9.1.1 fix the flaw, as do all releases published since. The latest versions available in November 2026 are PrestaShop 8.2.9 and 9.2.1.
On PrestaShop 1.7, the fastest fix is the official hotfix module pshotfix_ghsaw9f3qc75qgx9, published by PrestaShop and compatible with versions 1.7, 8.x and 9.x. It installs from the Module Manager, backs up the vulnerable file and applies the fix. Since no new 1.7 release is coming, you should then plan a migration to PrestaShop 8 or 9.
No. The update stops booby-trapped messages from working, but it does not remove a backdoor that is already installed. If your store stayed vulnerable, check Customer Service messages, the list of modules and employees, configuration files and the server’s outbound connections. If you find an intrusion, change every credential.
PrestaShop is secure in 2026 as long as it is kept up to date. The project has a public security policy, publishes advisories and ships fixes quickly, often with a hotfix module for older versions. Most hacks come from unpatched stores and from abandoned third-party modules, not from a well-maintained core. A store running a supported version, with few modules, regular backups and monitoring, is well protected.
Often, yes. In the United States, every state has a breach notification law with its own deadlines and triggers, and businesses must generally notify affected residents. In Canada, PIPEDA requires reporting breaches that pose a real risk of significant harm and notifying the people affected. In the UK and the EU, the regulator must be notified within 72 hours when the breach poses a risk.
EXCELLENT Based on 22 reviews Posted on Google pierre lenfantTrustindex verifies that the original source of the review is Google. Aurone is a web agency like no other! Very responsive, highly flexible in the way they work and always at the cutting edge of technology: you can count on real professionals for all your web projects!Posted on Google Sami Yassine TurkiTrustindex verifies that the original source of the review is Google. As Secretary General of the Lina Ben Mhenni association, it was a pleasure to work with the AURONE agency, which developed our website with great professionalism.Posted on Google Gwladys LavergneTrustindex verifies that the original source of the review is Google. Responsive, attentive and highly skilled: we are delighted to work with Aurone, who meet our expectations perfectly, both in graphic design and in technical expertise. I highly recommend their support!Posted on Google Perrine AmalTrustindex verifies that the original source of the review is Google. Aurone is a human, responsive and efficient company. The work was done quickly and promptly. I highly recommend them and hope to continue this collaboration in the future.Posted on Google Stephanie WillmanTrustindex verifies that the original source of the review is Google. We have been working with Aurone since 2016 and are delighted. We first called on their services for a project in Tunisia, and the quality of their work means we now rely on Aurone for services in other countries too. The team is dynamic, creative, responsive and enthusiastic. They have always understood our needs for our diverse and complex web presences, and do their best to meet them. Web platforms, training workshops on the platforms, video tutorials and graphic design for various products are just some of the excellent services Aurone provides. The technical quality of their web services is top-notch, and we always get good advice, both technical and creative. We highly recommend them.Posted on Google Raphaël GianassoTrustindex verifies that the original source of the review is Google. For your e-commerce and digital marketing projects, the Aurone team is attentive, experienced, available and responsive. A team you can count on, for whom customer satisfaction comes first.Posted on Google Samuel DechometsTrustindex verifies that the original source of the review is Google. At Aurone I found everything you can expect from a good web agency: quality, responsiveness, flexibility, relevance... Well done and thank you!Posted on Google Karim DjebbarTrustindex verifies that the original source of the review is Google. Our whole network worked with the Aurone agency for several years. A few adjustments were needed at the start of our partnership back then, but quality quickly followed.
The teams worked very professionally, adapting to the requirements of the French clients we soon put them in touch with.
A great deal of agility from its founder.
Thank you for these great years!
27 Avenue Taieb Mhiri, Immeuble Yasmina
2080 Ariana, Tunis, Tunisia
Made with in Tunis | Copyright © 2007-2026 Aurone | Legal notice | Privacy policy | Shop