Service

Web & PHP Code Auditing

Deep-dive security audits of PHP applications, Laravel codebases, and web platforms. We go beyond automated scanning to manually review your source code for injection flaws, authentication bypasses, and business logic vulnerabilities.

Detail

Manual line-by-line auditing of your PHP codebase. SQL injection, mass assignment, insecure deserialization, broken access control, and framework-specific misconfigurations in Laravel, Symfony, and vanilla PHP.

What we cover

Injection

SQL injection, command injection, and unsafe deserialization across every input path into the application.

Access control

Broken object-level authorisation, privilege escalation, and routes that trust client-supplied identifiers.

Authentication

Session handling, password and token storage, multi-factor gaps, and account recovery flows.

Framework misuse

Mass assignment, unguarded models, disabled CSRF protection, and unsafe Blade or Twig output.

Business logic

Workflow bypasses, race conditions, and pricing or quota logic that can be driven to an unintended state.

Dependencies

Known vulnerabilities in Composer packages, plus abandoned and unpatched libraries still in production.

Automated scanners are good at finding the vulnerabilities that look like vulnerabilities. They are poor at understanding what your application is for, which is where the expensive flaws live. A scanner cannot tell you that a user with a valid session can read another tenant's invoices by changing a single identifier, because nothing about that request is malformed. Catching that takes somebody reading the code.

How we approach a code audit

We start with the parts of your codebase that decide who may do what: authentication, authorisation middleware, and the routes that sit behind them. From there we follow the data, tracing every path from user input through to a database query, a filesystem call, a template, or a shell. Where a path looks exploitable we build a working proof of concept against a non-production environment, so you get evidence rather than a theory.

Source access matters here. When we find an unescaped output or a missing authorisation check, we grep for the same mistake everywhere else in the codebase and report it as one finding with every occurrence listed.

Stacks we work with

We audit Laravel, Symfony and vanilla PHP applications, including long-lived legacy codebases that have grown through several framework generations. We know these stacks because we build on them ourselves, which means we recognise the idioms that are merely unusual and the ones that are actually dangerous.

Legacy is not a disqualifier. Some of our most valuable work has been on applications a decade or more old, where the original authors are long gone and nobody still on the team is certain what a given module does.

What you get

01

A written report with every finding rated by severity and mapped to its root cause

02

A reproducible proof of concept for each exploitable issue

03

Prioritised remediation guidance written for the developers who own the code

04

A follow-up review of your fixes once remediation is complete

Every engagement starts with a conversation about scope. Tell us what you have built and what worries you about it, and we will tell you what a useful assessment looks like.