CVE-2022-0220

The check_privacy_settings AJAX action of the WordPress GDPR WordPress plugin before 1.9.27, available to both unauthenticated and authenticated users, responds with JSON data without an "application/json" content-type. Since an HTML payload isn't properly escaped, it may be interpreted by a web browser led to this endpoint. Javascript code may be executed on a victim's browser. Due to v1.9.26 adding a CSRF check, the XSS is only exploitable against unauthenticated users (as they all share the same nonce)

The check_privacy_settings AJAX action of the WordPress GDPR WordPress plugin before 1.9.27, available to both unauthenticated and authenticated users, responds with JSON data without an "application/json" content-type. Since an HTML payload isn't properly escaped, it may be interpreted by a web browser led to this endpoint. Javascript code may be executed on a victim's browser. Due to v1.9.26 adding a CSRF check, the XSS is only exploitable against unauthenticated users (as they all share the same nonce)

La acción check_privacy_settings AJAX del plugin GDPR de WordPress versiones anteriores a 1.9.27, disponible tanto para usuarios no autenticados como autenticados, responde con datos JSON sin un tipo de contenido "application/json". Como la carga útil HTML no es escapada correctamente, puede ser interpretada por un navegador web que conlleve a este endpoint. El código Javascript puede ser ejecutado en el navegador de la víctima. Debido a que la versión v1.9.26 añade una comprobación de tipo CSRF, un ataque de tipo XSS sólo es explotable contra usuarios no autenticados (ya que todos comparten el mismo nonce)