Website Security and Health Report
| Site assessed | A fictional shop (demo site) · example-shop.test |
| Type of assessment | External surface review (not signed in) — the $129 package |
| Date | 1 August 2026 |
| Valid until | 31 August 2026 (30 days — after that it is worth re-running, because sites change and new holes appear) |
| Tooling | raidkit + raidscan (source public on GitHub) alongside manual testing |
| Assessor | Phisit Tantiranon · ZyntronLabs |
01 Summary for the business owner
9 findings in total. One of them is critical and should be fixed today: the product search field lets anyone pull your whole customer list out without signing in. In priority order, three things matter.
- TodayClose the injection hole on the search field (finding 1). It is the only one through which customer data can actually leave right now.
- This weekLock down the admin area and set the session cookie flags (findings 2 and 3).
- When convenientClear the remaining configuration items and deal with the product page taking 4.6 seconds on mobile.
| Severity | Count |
|---|---|
| Critical | 1 |
| High | 2 |
| Medium | 3 |
| Low | 2 |
| Advisory | 1 |
| Total | 9 |
02 Findings, one at a time
Each one states the business impact in plain language, then the fix your developer can act on straight away. CVSS is the standard severity score from 0 to 10.
The product search field lets commands through to the database (SQL injection)
CVSS 9.1CriticalTyping a specially crafted string into the search box pulls out your entire customer list — names, phone numbers, addresses and order history — with nobody signed in. Confirmed on a test account. No real customer data was touched.
FixMove every query that takes user input to parameterised statements. Never concatenate input into a query string. This is a fix in the code, not a setting.
The admin area is reachable without a second identity check
CVSS 7.5HighThe /admin path is guessable, and once inside the system does not limit what each user level can see. An ordinary staff account can read sales figures and customer records for every branch, when it should only see its own.
FixEnforce permissions on the server for every admin route rather than hiding buttons in the interface, and require two-factor authentication on any account that reaches customer data.
The session cookie has no security flags set
CVSS 7.4HighThe cookie proving who is signed in is missing HttpOnly and Secure. A script on the page, or anyone listening on public Wi-Fi, can take it and act as that customer or administrator.
FixSet HttpOnly, Secure and SameSite=Lax on every cookie tied to sign-in. This is a server configuration change and takes minutes.
The site announces its software and server versions to anyone
CVSS 5.3MediumResponse headers publish the exact versions in use. An attacker reads them and immediately knows which publicly known holes for that version are worth trying, which removes the slowest part of their work.
FixStop version numbers appearing in HTTP headers and error pages.
Your pages can be framed inside someone else's site (clickjacking)
CVSS 5.4MediumAn attacker loads your page underneath an invisible layer of their own and gets your customer to click something they never intended, such as confirming an order or changing an account setting.
FixAdd Content-Security-Policy frame-ancestors and X-Frame-Options.
The checkout page loads some scripts without encryption
CVSS 4.8MediumThree resources on the payment page load over plain http. Modern browsers warn about it, which makes customers hesitate at the exact moment they were about to pay, and it lets those files be altered in transit.
FixServe every resource on the page over https.
No robots.txt is published
CVSS 3.1LowNot a security hole in itself, but you have no control over which pages search engines index.
FixAdd a robots.txt naming the paths you do not want indexed, such as the admin area.
No meta description on key pages
CVSS 2.6LowGoogle picks arbitrary text from the page for the search result, and people do not click it.
FixWrite a short, inviting description for every page that matters.
03 Speed and site health
| Page | Mobile | Desktop | Result |
|---|---|---|---|
| Home | 2.1 s | 0.8 s | Pass |
| Product list | 4.6 s | 1.9 s | Too slow on mobile |
| Checkout | 3.8 s | 1.4 s | Worth improving |
The product page takes 4.6 seconds on mobile. Past three seconds people start leaving, so every extra second is customers who never reach your products. That is not a security matter, but it hits revenue directly.
04 Everything that was tested
The list below is everything checked, not only what turned up a problem. An item with no finding means your site passed it, which is worth knowing too.
| OWASP Top 10 (2021) | |
| ✓ | A01 Broken access control |
| ✓ | A02 Cryptographic failures |
| ✓ | A03 Injection (SQL, NoSQL, command) |
| ✓ | A04 Insecure design |
| ✓ | A05 Security misconfiguration |
| ✓ | A06 Vulnerable and outdated components |
| ✓ | A07 Identification and authentication failures |
| ✓ | A08 Software and data integrity failures |
| ✓ | A09 Security logging and monitoring failures |
| ✓ | A10 Server-side request forgery |
| Encryption and certificates | |
| ✓ | HTTPS enforced everywhere, with http redirected |
| ✓ | SSL certificate validity and expiry |
| ✓ | TLS versions and cipher suites offered |
| ✓ | HSTS header |
| ✓ | Mixed content |
| Security headers and cookies | |
| ✓ | Content-Security-Policy |
| ✓ | X-Frame-Options and frame-ancestors |
| ✓ | X-Content-Type-Options |
| ✓ | Referrer-Policy and Permissions-Policy |
| ✓ | Cookie flags: HttpOnly, Secure, SameSite |
| ✓ | Software versions disclosed in headers |
| Personal data exposure (GDPR and PDPA) | |
| ✓ | Personal data reachable without authentication |
| ✓ | Personal data sent over unencrypted channels |
| ✓ | Consent capture and privacy policy pages |
| ✓ | Data leaking through URL parameters |
| Site health and speed | |
| ✓ | Server response time on mobile and desktop |
| ✓ | Page weight and resources loaded |
| ✓ | Mobile viewport configuration |
| ✓ | Page titles and descriptions for search results |
| ✓ | robots.txt and sitemap.xml |
Certificate of Security Assessment
The website example-shop.test was assessed for security and site health against the OWASP Top 10 and personal data protection requirements on 1 August 2026. Every finding was reported together with a fix. This certificate confirms the assessment took place. It is not a claim that the site is free of every possible weakness, and the owner may show it to their own customers.
Want this for your own site?
The full report for your real site is $129, delivered within three working days, with the certificate included.