Arbitrary Code Execution Affecting johnpbloch/wordpress package, versions >=5.4.0, <5.4.1>=5.3.0, <5.3.3>=5.2.0, <5.2.6>=5.1.0, <5.1.5>=5.0.0, <5.0.9>=4.0.0, <4.9.14>=4.8.0, <4.8.13>=4.7.0, <4.7.17>=4.6.0, <4.6.18>=4.5.0, <4.5.21>=4.4.0, <4.4.22>=4.3.0, <4.3.23>=4.2.0, <4.2.27>=4.1.0, <4.1.30>=4.0.0, <4.0.30>=3.9.0, <3.9.31>=3.8.0, <3.8.33>=3.7.0, <3.7.33

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

The vulnerable system can be exploited without interaction from any user.

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

There is no loss of confidentiality within the impacted component.

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

There is no impact to availability within the impacted component.