Close the gaps attackers look for
Shopify secures checkout, payments and its servers. What gets added on top, such as theme code, old scripts and apps, is where stores leave doors open. We find those gaps from the outside and fix them in your theme.
Who looks after what
Shopify covers the platform. The rest is yours.
Shopify looks after
- Servers and hosting
- Checkout and payments
- SSL certificates for your domain
- Updates to the Shopify platform itself
You and your developers look after
- Theme code and custom sections
- Apps and the scripts they add
- API keys and staff accounts
- Chat, review and tracking tools from other companies
This is where AccessFix helps.
What we fix
The most common open doors
Most of these come from apps installed years ago or code pasted in during a quick change.
Old scripts with known bugs
Outdated jQuery, Bootstrap and similar libraries, often added by apps, have published bugs attackers know how to use. We update or remove them.
Secret keys left in page code
API keys pasted into theme code can be read by anyone. We find them, help you revoke them and move them out of the theme.
Unsafe loading and missing protection
Files or forms sent without encryption, pages that can be framed by other sites, and apps you forgot about.
Every free scan
Six checks, in plain English
Each finding in the report says what an attacker could do with it and how to fix it.
| Check | What we look at | Typical risk |
|---|---|---|
| HTTPS and redirects | Every page is encrypted, and plain http:// visits are sent to https://. | High |
| Outdated libraries | jQuery, jQuery UI, Bootstrap, Lodash and Moment.js versions compared with published security bugs (CVEs). | Medium |
| Exposed secret keys | Shopify Admin tokens, Stripe secret keys, AWS keys, private keys and similar, in page code or the store’s own scripts. | High |
| Unencrypted files and forms | Scripts, images or forms loaded or sent over plain http:// on a secure page. | Medium–High |
| Security headers | HSTS, clickjacking protection, file-type sniffing and a Content Security Policy. | Low–Medium |
| Third-party scripts | A list of every other company whose code runs on your store, so you can remove what you no longer use. | Info |
How far we go
Passive by default. Deeper only with permission.
Free scan · no permission needed
We look, we never touch
- Only what any visitor’s browser already receives
- No attack attempts, password guessing or hidden pages
- Public pages only, at a normal browsing pace
Security review · written permission
A closer look, agreed in advance
- Installed apps and the permissions they hold
- Staff accounts and two-step login
- Theme code that prints customer input unsafely
- Custom forms and integrations
Published bugs
Library versions we flag
These versions have security bugs listed in the public CVE database. Apps often load an old copy without anyone noticing.
- jQuery below 3.5.0
CVE-2020-11022, CVE-2020-11023- jQuery UI below 1.13.2
CVE-2021-41182, -41183, -41184, CVE-2022-31160- Bootstrap below 3.4.1, and 4.0 to 4.3.0
CVE-2019-8331- Lodash below 4.17.21
CVE-2021-23337- Moment.js below 2.29.4
CVE-2022-31129
Responsible disclosure
Found a problem on our site?
Email hello@accessfixhq.com with what you found and how to see it. We reply within 2 working days, fix confirmed issues as fast as we can and credit you if you would like. Please don’t access other people’s data or disrupt the site while testing. Our security.txt has the same details for automated tools.
Keep reading
Free scan
Check your store from the outside
Enter your store address and create a free account. We check your key pages for accessibility barriers and security gaps and send a plain-English report within 2 working days.