Skip to main content


Holy shit

wp2shell (CVE-2026-63030 & CVE-2026-60137) - full RCE chain

" Independent proof-of-concept for the unauthenticated WordPress REST batch route-confusion SQL injection associated with Searchlight Cyber's wp2shell advisory."

github.com/Icex0/wp2shell-poc

#WordPress #RCE

in reply to Milo

@milo
Using the Internet is a security risk. Server or client.
@Milo
in reply to Ray McCarthy

@raymaccarthy Given how often critical security vulnerabilities are reported in WordPress core and plugins, this simply poses too great a security risk compared to other CMSs
in reply to Milo

@milo @raymaccarthy WordPress is a little over the top the last few years.. I mostly use Ghost now but rather just Laravel and build it myself, no unneeded bloated code that can be a security risk
in reply to stux⚡️

@milo
People need to not madly add plugins, which increase the vulnerability, assuming not actually malware.

Some other CMS are dreadful to update. Especial Drupal or Mediawiki. So people don't update!

Adobe Commerce used to be Magneto and was terrible for vulnerabilities?

Wordpress suffers from the exposure of being the most popular? Your own install with custom .htaccess and file permissions (especially on upload directories).

@Milo
in reply to stux⚡️

I discussed this a number of days ago. A site to test vulnerability, and a plugin to block the exploit if you can't or don't want to upgrade wp, is here: wp2shell.com/
in reply to stux⚡️

I thought the whole thing of WordPress was being CVE first, CMS second.