Dependency & CVE scan
composer audit against known security advisories, plus a review of outdated and abandoned packages and bundles that block the upgrade.
Symfony security audit & upgrade
A fixed-price Health & Upgrade Audit of your Symfony application: known vulnerabilities, deprecations, PHP compatibility and security configuration, plus a step-by-step roadmap to Symfony 7.4 LTS with a fixed upgrade quote.
Why now
Symfony 6.4 LTS stops receiving bug fixes in November 2026, and PHP 8.2 stops receiving security fixes on 31 December 2026. Apps on Symfony 3.4 or 4.4 have had no framework security fixes since 2021 and 2023. For most business applications the sensible landing version is Symfony 7.4 LTS, supported with security fixes until November 2029.
Dates from symfony.com/releases and php.net/supported-versions.php, checked November 2026. Symfony 5.4 security support was extended to February 2029, but third-party bundles are already dropping it.
The offer
composer audit against known security advisories, plus a review of outdated and abandoned packages and bundles that block the upgrade.
Every deprecation your code and bundles trigger on the way to 7.4, grouped by effort, with a Rector dry run to show what can be automated.
What breaks on PHP 8.3 / 8.4, which extensions and libraries need attention, and how to get off PHP 8.2 before its security support ends.
Firewalls and access control, voters, CSRF protection, session and cookie settings, and how secrets and environment variables are handled. A focused review, not a penetration test.
A version-by-version path to Symfony 7.4 LTS, the risks we found, and a fixed price for doing the upgrade ourselves.
The audit fee is credited 100% toward the upgrade if you order it within 30 days of the report.
Book the auditQuoted as a fixed price from the audit findings, so you know the cost before work starts.
A monthly retainer for Symfony and PHP security releases, dependency updates and monitoring once you are on a supported version.
Method
Upgrades fail when they are done as one big jump. We move in small, tested, reversible steps.
Rector and the Symfony rule sets handle the repetitive code changes, so review time goes to the parts that need judgment.
For example 4.4 → 5.4 → 6.4 → 7.4, clearing deprecations at each step before the next major. Each hop is a working, deployable state.
Where coverage is thin, we add functional and characterization tests on the critical paths (login, checkout, APIs) before changing the framework underneath them.
Every step goes to a staging environment first, then production with a rollback plan. No long-lived upgrade branch that never ships.
FAQ
Symfony 2.x through 7.x. The usual starting points are 3.4, 4.4, 5.4 and 6.4, and the usual target is 7.4 LTS.
No. It is a code and configuration review: dependencies and known CVEs, firewalls, voters, CSRF, sessions and secrets. If you need a penetration test, we will say so in the report.
Read access to the repository, the composer.json and composer.lock in use, the PHP version in production, and a short call about how the app is deployed. Production access is not needed for the audit.
Standard Symfony releases are supported for about eight months; 7.4 LTS gets security fixes until November 2029. Most business apps should land on the LTS and plan the next hop calmly.
As a fixed price, based on what the audit finds. If you order it within 30 days of the report, the €1,900 audit fee is credited in full.
Yes. We work in small steps that merge back regularly, so your team is not blocked by a long-running upgrade branch.
Book the audit
Share the versions you run and what worries you. We reply by email with next steps and a start date for the audit.
Prefer email? contact@webbamboo.net