As mentioned above, it has already been mitigated on lemmy.world
So there should not be any reason to defederate [from lemmy.world]. I will continue monitoring and investigating, if further vulnerabilities pop up then I will adjust accordingly.
Shame lemm.ee wasn't around when I first propped up the community. It was literally just the big three (ml, grad, beehaw) and world was barely a week old but I had faith in their background. One hopes this is just a minor blip in their radar.
Events like this make me more and more convinced that communities are better off dispersed among different instances, perhaps a bunch of related communities being bundled together in a themed/geographical instance. However, it's unfortunate that events like this also highlights the importance of knowledgeable and competent instance admins (on top of other technical requirements for running an instance, as well as the legal responsibilities of the choice of hosting location), thus establishing an instance, and administrating it is a heavy responsibility.
Judging from the github ticket, it seems like it's a vulnerability on all lemmy instances. But the attack can only happen on instances where the markdown editor has generated the sidebar etc with vulnerable HTML code. The devs still needs to patch the vulnerability to ensure it won't happen again.
Admittedly, this stuff is way over my head, but given the quick action I've seen thus far, I'm hopeful that it won't be long before this vulnerability would be patched.