科奉工作室

Kefong Studio

Crafting every piece with care

Kefong Studio is an independent software studio. We build practical systems for logistics companies, teams and individuals — available as SaaS, on-premises deployment or custom development.

Products

All products →

Latest articles

All articles →

The PHP vulnerability unearthed by AI made the bank take its site down that very night, and the same week there was a second landmine

These past two days, a bunch of websites worldwide have been doing emergency maintenance, triggered by two things: one is a PHP remote code execution vulnerability that AI helped uncover (CVE-2026-109618/109619, 9.2 score, no authentication required, mod_php is the most dangerous, and IIS's php-cgi is also on the list); the other is that the private keys of 8 of eMudhra's intermediate CAs can be computed (one of them has a value of 4), which amounts to a root-of-trust leak. Clearly explain the difference in nature and handling between the two, why Go/Java/Node/Python each rushed out updates overnight, why Java's 9.1 score is not RCE, how to make the changes on Windows/IIS, and that the real hit targets are the CA copies nobody looks after—containers, CI, and already-compiled binaries.

General-purpose AI agents have stopped running ads; only two paths remain for this industry going forward.

General-purpose AI agents are clearly receding, and many people think this field is done for. My judgment is that it is merely forking: one path leads to industry solutions, the other to a niche market of fully localized, bespoke offerings. It's not that the big players can't do the latter—they don't dare to—and precisely because of that, it will become a word-of-mouth business within circles. At the end of the article, I also lay out three conditions that could overturn this judgment.

Is this a fact, or a rule? — Using first principles in leading people, dealing with people, and running projects

First principles is often made out to be more mysterious than it is. It really only does one thing: break a problem down until it can't be broken down any further, and distinguish which parts are inherent constraints and which are merely things other people have told you. This piece is written for people who lead teams, deal with people, and manage projects every day—how to use it in four specific scenarios, and three occasions when you absolutely should not use it.