Website security check before launch: 12 points for a new webshop or website
A new webshop or website is worth checking for security before launch, because that is when fixing things is cheapest: there are no real customers, orders or customer data in it yet. The most common problems are not complicated: a leftover test account or backup file, test payments still switched on, another customer's order visible by changing a number, an outdated plugin. In this article we collected 12 points you can mostly check yourself, and we describe where you need a professional.
We checked the laws, standards and figures in their original sources on 20 November 2026; the list is at the end of the article.
Why before launch?
- It is cheaper. A bug found at the end of development takes an afternoon to fix; after a break-in you also pay for the recovery, for notifying customers and for the lost days of sales.
- There is nothing to steal yet. As long as there are no live orders and customer data, a bug is just a bug. Afterwards it can be a personal data breach.
- New sites are found quickly. Most attacks are not targeted: bots scan the web for known weaknesses and do not care how big the business is. According to a 2018 study, certificate transparency logs (they show when a new address gets https) are also used to start scanning new sites only minutes after the certificate is issued.
If the webshop processes personal data (name, address, phone number – a webshop always does), Article 32 of the GDPR requires technical and organisational measures appropriate to the risk, and regular testing of how effective they are. If something does go wrong, under Article 33 a personal data breach that poses a risk must be reported to the supervisory authority (in Hungary, the NAIH) without undue delay and, where feasible, within 72 hours. In Eurostat's 2024 survey, 13.7% of Hungarian enterprises with at least 10 employees had at least one ICT security incident (EU average: 21.5%), but only 13.8% of them had a written ICT security policy (EU: 35.5%).
What does the webshop platform do, and what is left to you?
What you need to check depends on what your site runs on.
| The site | Updating the server and the platform | What stays with you |
|---|---|---|
| Hosted webshop platform (e.g. Shoprenter, UNAS, Shopify) | the provider | admin accounts and two-step login, installed apps, pasted code (tracking, chat), payment and shipping settings, domain, email |
| WordPress + WooCommerce on your own hosting | you or your developer (the host only updates the server) | everything above, plus updating WordPress, the theme and the plugins, and backups |
| Custom-built site | the developer, if the contract says so | everything above, plus bugs in the code itself (permissions, payment confirmation, forms) |
Hosted platforms offer two-step login too, but you usually have to switch it on: in Shoprenter, for example, it is off for everyone by default, and in Shopify each staff member sets it up for their own account.
12 points before launch
Logins and accounts
- Everyone has their own account, with two-step login. Do not share one "admin" password. Before launch, delete or disable the accounts of the developer, the testers and former staff, and give the developer only the rights the job needs.
- No default or guessable logins. "admin / admin123", the password you got at installation, and also the hosting, database and domain registrar accounts. These passwords should be unique and should not travel by email or chat.
What may be left over from development
- The backup, the configuration file and version control cannot be downloaded. Try it in the browser with your own address: example.com/.env, example.com/.git/HEAD, example.com/backup.zip, example.com/phpinfo.php. If any of them downloads something or opens a page, that is a problem: these typically contain the database password and the full code. The right answer is "not found" (404) or "forbidden" (403).
- No test data or test keys left. Test orders, test customers, "test product 1", the payment provider's test mode (sandbox) and the test keys. Try the live payment once with a real card and a small amount, then refund it.
- Errors do not show the code. If a page fails, the visitor should see a short message, not the server's error output with file names and database details.
Payments and orders
- Card data does not arrive on your server. For a small business the safest option is that the customer enters their card on the payment provider's page (a redirect or the provider's embedded payment page). Since early 2025 the card payment standard (PCI DSS) has a separate condition for merchants whose site embeds the payment form: the site must be protected against scripts that could tamper with the payment page. So do not put unnecessary third-party code around the payment page.
- An order only becomes "paid" after a genuine confirmation. This is a common bug in custom builds: the webshop believes what the browser says and does not check the payment provider's signed notification. Ask your developer how it is checked.
- The server calculates the price. The price, the discount and the shipping fee must not come from a number sent by the browser. A simple test: two products in the basket, a coupon code twice, a negative quantity – what does the webshop do?
- Nobody can open someone else's order. If the order or invoice address contains a number (…/order/1043), change it to 1042 from another customer's account, or logged out. If it opens, another customer's name and address are visible. In the international ranking of web security risks (OWASP Top 10, 2025), this type of bug – broken access control – is number one.
Site, email, backups
- Everything is updated, and what is not needed is removed. With WordPress: the core, the theme and every plugin; a deactivated plugin left installed can still be attacked. According to Patchstack, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, 91% of them in plugins, and roughly half of the high-impact ones are exploited within 24 hours.
- Your emails arrive, and nobody else can send in your name. The domain needs SPF, DKIM and DMARC records; otherwise order confirmations end up in spam, and anyone can send email in your name. Since 1 February 2024 Gmail requires SPF or DKIM from every sender, and DMARC as well from anyone sending more than 5,000 messages a day.
- There is a backup, and you have tried restoring it. "The host makes backups" is not enough: you need to know where the site is restored from, how long it takes and what it costs. The domain and the hosting should be in your name (more on this: How much does it cost to maintain a website?).
What you can check yourself in 15 minutes
Only on your own site, or where you have permission:
- Security headers and https: Mozilla HTTP Observatory – gives a grade and tells you what is missing.
- The certificate and the encryption: Qualys SSL Labs.
- Leftover files: the addresses from point 3 in your browser.
- Email: send a test order to a Gmail address and check under "Show original" that SPF, DKIM and DMARC say "PASS".
- Someone else's order: the test from point 9 with two test accounts of your own.
What these do not reveal: bugs in the code. An external scanner looks at the finished site from the outside; it cannot see whether a form passes data to the database unchecked, or whether a password was left in the code.
Which check is good for what?
| Method | What does it find? | What not? | For whom? |
|---|---|---|---|
| Self-check (the 12 points above) | configuration mistakes, leftover files, test remnants | bugs in the code | everyone, before launch |
| External scanner (Observatory, SSL Labs) | missing headers, weak encryption, known issues visible from version numbers | the inside of the code, logic bugs | everyone, free |
| Source code review | leaked secrets, injectable code (SQL, XSS), dangerous uploads, outdated libraries | some permission and business logic bugs, pages behind the login | custom-built website, webshop |
| Penetration test (pentest) | a manual attack attempt against the live system, logic bugs too | whatever the scope of the engagement excludes | larger systems, lots of customer data, contractual requirement |
Is this the "NIS2" vulnerability assessment?
No. The Hungarian cybersecurity act (Act LXIX of 2024, which transposes the EU NIS2 directive) applies to organisations in the sectors listed in its annexes – there typically from medium-sized enterprises upwards (over 50 employees or EUR 10 million turnover) –, to public administration, to organisations designated by the authority, and regardless of size to a few providers such as domain registrars. An average small webshop or company website is therefore usually not covered; if you are unsure, section 1 and the annexes of the act decide.
For organisations covered by the act, the vulnerability assessment required by law may only be carried out by an organisation registered for it with the SZTFH (SZTFH Decree 5/2025 (VI. 20.)). COGMA is not on that register: our review is a voluntary check for small business websites and does not replace the assessment or audit required by law.
At COGMA
In a security review we go through your site's source code, on a copy of the code, in a test environment cut off from the network: leaked passwords and keys, downloadable files, injectable code, outdated libraries, and if you ask, the settings of the live site. We check the automated findings one by one, and you get a report in plain language that your developer can fix the issues from.
- Price: from €150 (larger systems from €300, re-check €50). We do not charge VAT because we are a VAT-exempt small business, so this is the full price.
- If we build your site, the review is part of the handover.
- For WordPress sites we review the custom theme and self-developed plugins; checking the installed plugins for known vulnerabilities is not part of the review yet – we say so in the quote.
- For hosted webshop platforms (Shoprenter, UNAS, Shopify) we do not get or review the platform's code; there, it is the settings from the 12 points above that are worth going through.
A real example from our own clients: on Hársfa Massage's WordPress site, the review on 31 October 2026 returned 27 findings – 20 missed updates, 6 vulnerable plugins and an outdated WordPress core. Here is how we moved it to our own engine.
Tell us what kind of site it is, and we will tell you what we can check and what it costs.
Frequently asked questions
What should you check on a new webshop before launch?
The logins (an account for everyone, two-step login, test and developer accounts removed), leftover files (backups, configuration files, the .git folder), that test payments are switched off, that an order is only marked paid after the payment provider's confirmation, that another customer's order cannot be opened, the updates, the email SPF/DKIM/DMARC setup and restoring the backup.
How much does a website security review cost?
With us, reviewing a smaller website costs from €150; for a webshop, booking system or other larger system we quote in writing after seeing the code. A re-check after the fixes is a separate, smaller fee. A penetration test typically costs several times as much, because it is several days of manual work.
Do I need to care about security on a hosted platform (Shoprenter, UNAS, Shopify)?
Updating the server and the platform is the provider's job, but the admin accounts, two-step login, installed apps, pasted code, payment settings, the domain and email are your responsibility. These are worth going through before launch.
Is https enough?
No. https only means that the connection between the browser and the server is encrypted. A downloadable backup, a test account or an attackable form can still be there.
What is the difference between a security review and a penetration test?
A review checks the source code and the settings for known types of bugs, with automated tools and manual review. A penetration test is a manual attack attempt against the live system lasting several days, which also looks for logic bugs, and typically costs much more.
Is a vulnerability assessment mandatory for a small webshop?
The vulnerability assessment under the Hungarian cybersecurity act (Act LXIX of 2024) is for organisations covered by the act – in the listed sectors typically from medium-sized enterprises upwards –, so it usually does not apply to an average small webshop. The GDPR, however, requires every webshop that processes personal data to take security measures appropriate to the risk and to test them regularly.
Sources
- Hungarian National Legislation Database: Act LXIX of 2024 on the cybersecurity of Hungary – section 1 (scope), annexes 2–3; accessed 20 November 2026.
- Hungarian National Legislation Database: SZTFH Decree 5/2025 (VI. 20.) – register of organisations entitled to carry out vulnerability assessments; accessed 20 November 2026.
- EUR-Lex: Regulation (EU) 2016/679 (GDPR) – Articles 32 and 33.
- NAIH: Data breach notification system – accessed 20 November 2026.
- Eurostat: isoc_cisce_ic and isoc_cisce_ra – 2024, enterprises with at least 10 employees (excluding the financial sector), updated 15 June 2026; accessed 20 November 2026.
- PCI Security Standards Council: Important Updates Announced for Merchants Validating to Self-Assessment Questionnaire A (30 January 2025) and the related FAQ; accessed 20 November 2026.
- OWASP: Top 10:2025 – accessed 20 November 2026.
- Patchstack: State of WordPress Security in 2026 – data for 2025; accessed 20 November 2026.
- Google: Email sender guidelines – accessed 20 November 2026.
- Shoprenter: Two-step authentication in Shoprenter (Hungarian); Shopify: Two-step authentication – accessed 20 November 2026.
- Scheitle et al.: The Rise of Certificate Transparency and Its Implications on the Internet Ecosystem, IMC 2018.
- Our own data: security review of Hársfa Massage, 31 October 2026.