Improper Access Control 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 basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

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

An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

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.