We know how WooCommerce, Magento and PrestaShop behave — and where custom-built e-shops most often fail. We'll find out whether your customers have an exposed session, whether the payment redirect holds HTTPS, and whether your cookies are GDPR-compliant.
We detect the platform — WooCommerce, Magento, PrestaShop or custom.
Cookie attributes, GDPR/ePrivacy, payment redirect, mixed content, exposed configuration files.
For each finding we explain what's happening and where the developer needs to look to fix it.
E-shops deal with different things than blogs. Sessions, payments, cookies, GDPR. Here are 6 problems we see most often on e-shops.
The cookie with the session ID travels over HTTP. On public Wi-Fi an attacker takes over the customer's account.
Set-Cookie: PHPSESSID=…; Path=/
Between the cart and the payment gateway there's one step over HTTP. An attacker in the network can redirect it elsewhere.
301 http://gateway/pay (downgrade)
Third-party cookies (Google Analytics, Meta Pixel) are set before the consent banner is shown. A regulator fine is almost certain.
Set-Cookie: _ga, _fbp (before consent)
Older browsers (Safari < 13) are vulnerable to CSRF. An attacker will send you an order in the customer's name.
SameSite: not set
An image from http:// is blocked by a modern browser. The visitor sees a broken page; the owner knows nothing.
img src: http://cdn.example/foto.jpg
Without HSTS the first visit often goes over HTTP. An attacker in a hotel or café exploits it.
Strict-Transport-Security: (missing)
https://gpwebpay.cz). The gateway itself is monitored by the bank.The PDF report tells you exactly where your e-shop has holes — and what specific step leads to a fix. Works on open-source platforms (WooCommerce, Magento, PrestaShop) and custom-built e-shops.