Keeping pace as AI speeds up the clock

AI is finding far more bugs and vulnerabilities, and the consequences are increasingly visible. Recent coverage of the PHP2Shell vulnerabilities showed how websites were taken offline as a precaution. While there’s hype, there’s also the harsh truth that the time from disclosure to exploitation has fallen from about three weeks in 2025 to under a day in 2026.

 

A faster clock doesn't mean more technical debt

A well-built Sitefinity upgrade from 2025 or a new front-end redesign from early 2026 is still well built.  What has changed is how often everything around it moves, and a Sitefinity estate has three layers that each move on their own schedule.

The platform moves every few weeks. Microsoft is pushing updates at a larger rate. NextJS is continuously releasing.  Progress has now adopted a release cadence of a steady stream of product updates, many with cumulative security fixes on a 2–3-week cycle instead of quarterly releases just 12 months ago.

All of this lands on the same team. Every Sitefinity update needs testing, every runtime change needs a slot in the plan, and every critical advisory now asks for a response within hours. Since 11 September, the EU Cyber Resilience Act has also introduced 24-hour early reporting obligations for manufacturers of products with digital elements when they become aware of actively exploited vulnerabilities. While these obligations don't apply equally to every website owner or development team, they reinforce a wider shift: security monitoring, assessment and response are becoming continuous responsibilities, not occasional maintenance tasks. 

The challenge isn't simply that more vulnerabilities are being discovered. It's that teams have less time to assess, prioritise, test and deploy the fixes that actually matter.

That means more budget and more hours than most 2026 plans allowed for, landing on development teams already stretched between feature work and their backlog.

 

We started with our own build

Earlier this year started looking at what we could do and reviewed our own Sitefinity renderer frontend build. It worked, and we changed it anyway. The result: a lean, pinned and reproducible build (For more information read our article 15 tips for Sitefinity frontend build modernisation ). From there, we looked at the broader aspects and how we could formalize an approach. Stricter CI gating, we’ve strengthened our security approach and tested ai-driven adversarial reviews.

 

What we set up

Patching isn't new to us. We've previously run large Sitefinity estates for years, where an update wasn't finished until it had reached every site and every language of the platform. What's new is the pace, so we've used that experience to build a workflow designed for it.

Over the past months we've turned it into a complete service that fixes what's exposed and also reduces what's reachable in the first place.

Starting with inventory and mitigation of outstanding issues and outdated components. From there we set standards and boundaries for regression and future dependencies and implement the automation of these checks. From there we setup the monitoring and pre-emptive landscape sweep so we know what needs updating, what can be safely addressed and having the expertise to act in advance and updates reach production in time.

 

Two ways to work with us

If you have a development team, they keep ownership. We help design the workflow, modernise the build where it needs it and act as second line for Sitefinity-specific problems. Our co-founder Sabrie spent four years in Sitefinity technical support at Telerik, and as a Progress Trusted Service Delivery Partner we can escalate to the vendor when a patch behaves unexpectedly.

If you don't have the capacity in-house, we run the workflow for you: monitoring, applying, testing and reporting, with you approving what goes live.

Either way, we start with a short conversation about your setup: Sitefinity version, hosting, renderer type, how much of the frontend was custom-built and how updates are handled today. That's enough to tell you where you stand and which route fits.


Talk to us about your Sitefinity update workflow →

getting things done, sitefinity

 


 

Explore other related latest insights, videos and news