15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform

Adobe Commerce 2.3.x Reaches End of Support

Final day of support for the 2.3.x release line. Merchants still on 2.3 should prioritise upgrade planning.

6 min
Adobe Commerce 2.3.x Reaches End of Support

8 September 2022 marks the official end of support for Adobe Commerce 2.3.x. This is the final day Adobe will issue security patches, quality fixes, and technical support.

What End of Support Means

After this date, Adobe will no longer issue security patches, provide quality fixes, offer technical support, guarantee compatibility, or update dependencies for 2.3.

Security Risk Timeline

Immediately after: Many vulnerabilities are fixed in newer versions. Running 2.3 means inheriting known risks. At 6-12 months: New vulnerabilities begin being discovered. At 1-2 years: Gap is significant, PCI DSS compliance becomes difficult.

Why 2.3 Support is Ending

Adobe Commerce 2.3 was released February 2019—over three years ago. Major improvements in security frameworks, performance, GraphQL, dependency management, and cloud infrastructure justify ending support.

Upgrade Paths from 2.3

To Adobe Commerce 2.4.x is standard. Version 2.4.0 released November 2020, with 2.4.5 (current) in August 2022.

Planning Your Upgrade

Audit codebase. Assess infrastructure. Develop test plan. Allocate resources. Stage migration. Schedule downtime.

Business Case for Upgrading

Performance improvements, modern payment integrations, GraphQL support, operational stability, and future-proofing for 3 more years.

Final Call

If on 2.3.x, do not delay. Securing platform should be top priority. Cost of upgrading now is far lower than responding to breach later.

Want to read more insights?

View All Articles