Crossposted from the Knowledge Commons team blog.
-
Yesterday, we published a message to the Commons community explaining our recent downtime. In the interest of transparency, I want to dig a little further into what happened, how we responded, and what we have learned. The entire Commons team welcomes your feedback.
On the afternoon of October 1, 2026, an attacker began scanning our WordPress installation for security vulnerabilities. Unfortunately, there were vulnerabilities to be found; we have known for some time that a few of our dependencies (various pieces of lower-level software in our stack) had security issues, and we have been working over the last year to close those holes. Those issues could not be resolved by simply bumping the software to its next version, because every new version of a small piece of software brings with it the potential for breaking something unexpected in a complex network like ours. Not only are we operating with a complex codebase, but our users are building their sites on top of our platform, and updates run the risk of breaking what they have done. As a result, updating our codebase requires substantial effort to ensure that the upgrades are done safely, as well as to test the results and remediate any problems. That work was almost complete, but we ran out of time.