breakdance

A network attacker without an account can reach a Breakdance operation that lacks the required authorization check in versions before 2.7.

Breakdance is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is n/a through 2.7.1.

Breakdance 2.7.1 and earlier stores attacker-controlled fields content without sufficient sanitization and later outputs it without safe escaping. Public form submission makes the issue reachable without an account, allowing persistent script to execute when the affected content is viewed.

Breakdance is affected by a security weakness. Exploitation requires an authenticated contributor account. The resulting impact depends on how the affected component exposes the vulnerable operation.

Breakdance is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Breakdance is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

Breakdance is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Breakdance is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.