snuffleupagus VS wp_d_rymcg

I wonder if Snuffleupagus can block this exploit.

https://snuffleupagus.readthedocs.io/

Having had to deal with a PHP exploit and still dealing with it I was looking around and came across jvoisin/snuffleupagus: Security module for php7 and php8 with is a successor to suhosin.

Other than that we rely on quite a lot of things these days, notably ModSecurity and the OWASP Core Rule Set alongside some other heavy restricting of our apps. (the idea being that the app is safe on its own, but those act as extra layers of defense in case we fuck up something really badly in the app one day)

When it comes to your application: I don't know how tech-savvy you are, and I'm not sure if you're worried about someone breaking into your webapp, but you could look into setting up security extentions like snuffleupagus (PHP) and SpiderLab's ModSecurity WAF for Apache and nginx for which OWASP has a great, free ruleset

snuffleupagus is pretty cool, I highly recommend looking at the default rules if you're wondering what it's capable of: https://github.com/jvoisin/snuffleupagus/blob/master/config/default.rules There are some things in there that you might not know about php yet!

No, it's a module that hooks into php functions and offers some general harding (like refusing to execute files that could be written to by www-data) and allows more fine-grained control over disable_function, like setting filters/rules for some arguments. The default config shows how to mitigate certain bypasses for regular php.ini based hardening: https://github.com/jvoisin/snuffleupagus/blob/master/config/default.rules

If you are stuck on wordpress, consider using a static export plugin like wp2static [1]. I have been playing around[2] with a setup where the normal WP UI is protected behind HTTP Basic Authentication, and wp2static exports the public snapshot

[1] https://github.com/WP2Static/wp2static

[2] https://github.com/jessopb/wp_d_rymcg