

While this does not reduce the risk factor of a PHP PHP The web scripting language in which WordPress is primarily architected. It should be possible for an administrator to access their admin admin (and super admin) backend, even in case of a fatal error. The primary goal of the feature remains the same as it was originally: We would like to ensure that the approach is solid to proceed with before it is fully implemented. Please share it and request feedback, both from community members and people less active in the WordPress ecosystem – particularly security experts and hosting engineers. This post outlines the new proposed approach in detail. Multiple follow-up tickets were created to mitigate these issues, but eventually the team came to the conclusion that all these tweaks would have only slightly reduced the attack vector, rather than eliminating it.Ī completely new approach was required, which would require additional time to be planned and implemented. The frontend is a “non-protected endpoint”, for which plugins or themes should never be paused.


This was arguably the most severe concern, since, while plugins should absolutely validate parameters rather than causing a fatal error, many have weaknesses in this area. an attacker could intentionally use such requests to force pausing of a plugin. Following that, the plugin might throw an exception, causing the plugin to be paused – i.e. These can be free in the Plugin Directory or can be cost-based plugin from a third-party, for example with a request method or parameters that said plugin does not expect. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. They can extend functionality or add new features to your WordPress websites.
