Nice to see #YunoHost being widespread enough (at least on the Fediverse) to end up as a trending hashtag after the #PHP2Shell incident. Thanks for being so proactive, @YunoHost and of course @Ondřej Surý for patching PHP so fast.
Today's my birthday! So, a local business sent me a congratulation message via email, as usual. Only problem is, the picture is hosted on their WordPress and GUESS WHAT HAPPENED TODAY so it links to a site currently down for maintenance. #PHP2Shell
Today I learned InfoSec's acronym for "did this exploit actually hit me while I was asleep?" is IoC (Indicators of Compromise) and I'm currently searching for those on the #PHP2Shell case. Because it turns out it might have been actively exploited all the way since JUNE!
@Profoundly Nerdy An earlier version of this advisory claimed that IoC checks should be performed "going back at least to June 2026", but it has since been updated. aikido.dev/blog/critical-vulnerabilities-in-php-php2shell
Either this vuln checker is flawed, or the standard #YunoHost security checks might have saved me from the #PHP2Shell . The results were "inconclusive" both before and after upgrading, so, who knows? php2shell.aikido.io/
like this
OK, the patched versions just arrived. No signs of exploit so far, but I will be checking during the course of the day.
J Miller
in reply to Carlos Solís • • •Amandine
in reply to Carlos Solís • • •