Every breach
has a file.
Cerberos watches small-business websites around the clock, finds the weak spots and fixes them before an attacker can use them.
Case 001 is an illustrative reconstruction.
Tuesday, 02:14:07
I. First contact
It didn't guess. It read.
An automated AI agent opens mira-bakery.example. It works through sites like this one all night.
It reads the page source, the same text every browser receives. Three version numbers are sitting in it.
It looks them up. The contact form plugin has a flaw that was published, with a description, years ago.
It writes a request that uses the flaw. No password needed.
It is in. It can change the site, read every order, or quietly add a fake payment page.
Illustrative. The method is documented in public research.1
4 minutes
12 seconds.
From first visit to full control. Nobody was watching.
II. What would have seen it
It was visible 41 days earlier.
Cerberos reads your website the way an attacker does: every page, every version number, every day. The difference is what happens next.
WordPress 5.8flagged. Two years of security updates missing.contact-form 2.1.0flagged. A published flaw, the one used in chapter I.slider 1.3.0flagged. Nobody maintains it any more.
Day 1, 09:00
III. Found, then fixed
Every finding comes with its fix.
A report full of red is not security. We fix what we find, then check again that the fix held.
| Finding | What it means for you | What we did | Status |
|---|---|---|---|
WordPress 5.8 |
Its published flaws apply to your site, and anyone can look them up. | Updated to the current release. The version number no longer shows on the page. | Fixed, day 1, 10:05 |
contact-form 2.1.0 |
The exact flaw used in chapter I. | Updated to 2.4.3 and the form tested again. | Fixed, day 1, 10:40 |
slider 1.3.0 |
Nobody maintains it, so its next flaw will never be fixed. | Replaced with a maintained gallery. | Fixed, day 1, 14:15 |
| Staff login open to everyone | Password guessing can run day and night, unnoticed. | Login limited, and two-step sign-in turned on for every account. | Fixed, day 2, 09:30 |
| Certificate expires in 12 days | Browsers would warn your customers away from your site. | Renewal automated, and checked again. | Fixed, day 2, 09:45 |
| After day 2, the watch goes on. | |||