Security

Adobe patches critical ColdFusion and Campaign Classic flaws

Adobe released patches this week for multiple maximum severity security flaws affecting Adobe ColdFusion and Adobe Campaign Classic. Neither product made headlines the way a browser zero day would, which is exactly why they are worth flagging: ColdFusion in particular still runs a surprising number of enterprise backend systems that nobody thinks about until something goes wrong.

Why this one matters

ColdFusion has a long history of being an attacker favourite precisely because organisations forget it is still running. If your business has a ColdFusion application anywhere in its stack, and plenty do without realising it, this patch round deserves the same urgency as a flashier vulnerability.

The attraction is a specific combination of properties. ColdFusion applications are usually web-facing, because serving web applications is what the product does. They typically hold database credentials, since they were built to put a front end on business data. They run on the Java platform, which brings a well-understood class of deserialisation weaknesses that attackers have tooling for. And they are old, which means the people who built them have frequently left.

Forgotten software is the most dangerous kind

The pattern that produces incidents is not an organisation deciding to accept risk on ColdFusion. It is an organisation not knowing it has ColdFusion at all.

A departmental reporting tool built in 2012 that still works does not generate tickets, does not appear in anyone's objectives, and does not get mentioned in architecture reviews. It sits on a server someone else now administers, serving a handful of users who would complain loudly if it vanished. Nobody is tracking Adobe's security bulletins on its behalf.

This is not hypothetical history. ColdFusion flaws have been added to CISA's Known Exploited Vulnerabilities catalogue more than once, and CISA has published advisories describing exploitation of ColdFusion at a federal agency where the affected servers were running outdated versions. Ransomware crews have used ColdFusion as an entry point into networks via installations left unpatched for years.

Why the flaws keep being severe

There is a structural reason ColdFusion advisories tend to sit at the top of the severity scale rather than the middle. The product's job is to take input from a web request and act on it: query a database, read a file, render a template. A flaw in that machinery frequently means an attacker can direct those actions, and the gap between "unexpected input accepted" and "arbitrary code executed" is short in an application server.

Deserialisation is the recurring culprit. Java applications routinely convert objects to a transmittable form and back again, and when untrusted data is converted back without strict validation, an attacker can supply something that executes during reconstruction. The technique is well documented with mature public tooling, so a newly disclosed deserialisation flaw does not need a skilled researcher to weaponise it.

How to find out whether this affects you

The useful work here is discovery rather than patching, because patching is straightforward once you know what exists.

Where to lookWhat you are looking for
External attack surface scanPorts 8500, 8300, or web paths containing /CFIDE/ and .cfm files
Web server configurationHandler mappings for .cfm or .cfc extensions
Software asset inventoryAny Adobe or Macromedia licence entries, including historical ones
Running services on serversJVM processes belonging to a ColdFusion install
Procurement and finance recordsRecurring Adobe renewals nobody can attribute to a current project
Load balancer and DNS entriesHostnames for applications no team claims ownership of

The last two rows find more forgotten systems than the technical scans do, because an application nobody remembers is usually still being paid for by someone. It is worth running the discovery across subsidiaries and acquired businesses as well, since inherited estates are where unmanaged legacy software concentrates and where nobody has ever held a complete inventory.

What to do

Check Adobe's security bulletin for the specific versions affected and patch on the normal enterprise change-control timeline, but do not let this slip to next quarter's list. Maximum severity ratings exist for a reason.

For anything you cannot patch quickly, reduce exposure instead. ColdFusion's administrator interface should never be reachable from the internet, and restricting it to an internal network or VPN removes a large share of the realistic attack paths on its own. Narrowing the database account the application uses to only the permissions it genuinely needs limits what a successful attacker reaches.

Campaign Classic deserves its own look rather than being treated as the lesser item in the bulletin, and it is frequently owned by marketing rather than IT, which is exactly how a patch notice ends up with nobody acting on it. Marketing automation platforms hold large volumes of customer contact data and send authenticated mail on your behalf, which makes a compromise both a data protection problem and a brand-impersonation one.

Do not forget the data behind it

One point that gets missed in patch-round coverage: these applications are usually interesting because of what they are connected to rather than what they are. A forgotten reporting tool is a low-value asset in isolation and a high-value one if it holds a read connection to a production customer database. When you find a ColdFusion install, record what it can reach, because that determines how urgent it is.

The timing argument

The case for not deferring this is about how fast exploitation now follows disclosure. Mandiant's research found the average time-to-exploit for vulnerabilities fell to about five days in 2023, down from 32 days across 2021 and 2022, less than a sixth of the time defenders previously had. Verizon's 2025 breach report puts vulnerability exploitation as the way in for 20% of breaches.

Regulators have adjusted accordingly, and we covered the point at which CISA's patch window came down to three days. The same compression shows up across this year's advisories, including an exploited Gitea flaw with a next-day deadline.

The costs make the arithmetic easy. Against the cost of a breach or a ransomware recovery, an out-of-cycle maintenance window on a legacy application server is inexpensive.

Key takeaways

  • Adobe patched maximum-severity flaws in ColdFusion and Campaign Classic. The products are unglamorous, which is precisely why the patches get deferred.
  • ColdFusion is attractive to attackers because installations are web-facing, hold database credentials, run on the JVM with known deserialisation weaknesses, and are usually old.
  • The real risk is not accepted risk but unknown inventory. Applications built a decade ago still work, generate no tickets, and have no owner watching vendor bulletins.
  • This has history. ColdFusion flaws have appeared in CISA's exploited-vulnerabilities catalogue, and CISA has documented exploitation at a federal agency running outdated versions.
  • Spend the effort on discovery. External scans for /CFIDE/ paths and .cfm handlers help, but unattributed Adobe renewals and ownerless DNS entries find more.
  • If you cannot patch immediately, take the admin interface off the internet and narrow the application's database permissions.
  • Do not defer. Average time-to-exploit fell to about five days in 2023, exploitation is the way in for roughly 20% of breaches, and a breach costs far more than a maintenance window.

More from Future Technology HQ