From our other sites
The story
A highly critical vulnerability has been discovered in PHP, the programming language widely used in web development, prompting a string of prominent services — including the childcare-facility SaaS “Kodomon,” the card game “Shadowverse: Worlds Beyond,” the online shop-building service “BASE,” and Sakura Internet’s rental servers — to go into emergency maintenance one after another on October 21, 2026. On 5ch, reactions split over what ordinary users should do right now, and over which companies got it “right”: the ones that moved fast, or the ones that were slow to react.
Prominent IT services rush into emergency maintenance one after another — Kodomon, Shadowverse, BASE, Sakura’s rental servers, and more — likely due to a “PHP” vulnerability
Prominent services including the childcare SaaS “Kodomon,” the game “Shadowverse: Worlds Beyond,” and “Sakura’s Rental Server” have gone into emergency maintenance one after another, or announced maintenance starting around 11pm that same night. This appears to stem from a highly critical vulnerability found in PHP, the programming language widely used in web development.
Other services expected to take similar action include the online shop-building service “BASE,” the rental server “X Server,” the online sales-event platform “pictSQUARE,” the official site of recycle shop “Kimble,” and the crowdsourcing site “Tsunagu.” Among these, Shadowverse: Worlds Beyond, Kimble, pictSQUARE, and BASE have confirmed — via their own announcements or reporting by ITmedia NEWS — that PHP is the cause.
Source: itmedia.co.jp / Original article here
What people said
Apparently it's a good idea to set up two-factor authentication in case your password gets leaked
Guess they learned nothing from last time's massive leak huh
Makes no sense
↓
"Actually, I'll tell you before the patch even drops! Here are the full details! This is the vulnerability!!"
↓
"AAAAAAAAAH wwwwwwwww" ← we are here
It's not like popping down to the corner store — there's no way exploiting this is that simple
It's not China. They'd have no reason to do it
Then who is it?
I know PHS (Japan's old cordless-phone standard), but PHP?
"Peace and Happiness through Prosperity"
It's a web programming language developed by a Japanese guy named Matsumoto Takahiro
It's pretty widespread
So basically this is Japan's fault
Da-da-da-DAAAAM wwww
Given the vibe, the place I work at is probably going under
Your company specifically, lmaooooo
(Correction: Ruby is the language made by Matsumoto Yukihiro)
Maybe a while back
But these days, with AI around, even an amateur can pull it off easily as long as they've got the knowledge
They can siphon off all your data, no limit
Free-for-all account takeovers
Lol
It's all over now
They're probably running on something other than PHP
It just means anyone can plant malware on it freely
So shutting sites down in the afternoon of October 21 is already way too late
There's definitely a mountain of leaked data out there by now, for sure
Yeah exactly
There are posts telling people to change their password, but isn't it already too late?
If that maintenance page itself is also running on PHP, isn't it the same problem?
I'd get it if it were the JRA (central) circuit, but blowing that much on a weekday is overdoing it
But small and mid-size companies that haven't even noticed yet are probably going to wake up tomorrow to find their homepages taken over across the board
Gonna be crawling with hackers' 'toys' by then
So the party starts tomorrow morning?
If you logged into any of them between October 20 and whenever they closed, you should just assume your info got stolen
If you reused that login password anywhere else, you're done
Change it right now
How are you supposed to change your password if the site's already closed?
Background and key points of debate
PHP is a server-side language used everywhere from personal websites to corporate core systems, and because so many services share the same underlying stack, a single vulnerability can spread its impact very quickly. The companies named in the article went into maintenance at the stage where they might be affected, and not all of them have officially confirmed the nature of the vulnerability. In the thread, two views run side by side: that “attacks are already underway, so taking countermeasures now is too late,” and that “the companies shutting down right now are actually the fastest to respond” — neither claim comes with verifiable evidence. For ordinary users, the real risk isn’t getting hit just by visiting an affected site; it’s account takeover if you reused a password from an affected service somewhere else. So the top priority right now is simply to stop reusing passwords across services.
*This article is excerpted and summarized from a 5ch (Nandemo Jikkyo G) thread titled “PHP vulnerability looking seriously bad. Sites that can’t respond by 11pm tonight are at risk of being taken over.”
Leave a Reply