OpenCart / ocStore Security Audit
OpenCart and ocStore security audit
An audit is needed in two situations: nothing has happened yet and you would like to keep it that way, or the site has already been cleaned and you need to confirm the hole was genuinely closed. This is an inspection, not a set of abstract recommendations: the output is a list of findings with severity ratings and a fix order.
What I check
- Versions and updates. Core, PHP, third-party modules — whether known vulnerabilities exist for those versions.
- Modules. I look separately for signs of pirated builds: they are the most frequent carriers of backdoors.
- Access. Administrators, permissions, the default admin URL, password strength, brute-force protection.
- Files. Permissions, what sits in the upload and image directories, and whether PHP can execute there.
- Server configuration. Whether configuration files, backups, service files and data directories are reachable from outside.
- Traces of presence. Web shells, suspicious administrators, modified core files.
- Headers and SSL. Certificate, security headers, mixed content.
What you receive
A report in three parts: critical (fix today), important (fix soon) and desirable. Every item explains what it threatens on your specific store and what exactly to do. I can carry out the fixes or hand them to your developer.
What the audit does not do
It is not an automated scan producing a boilerplate PDF. And it is not a guarantee the site cannot be broken into — no such guarantee exists. An audit shows the real state and removes the most likely attack scenarios.
