Vulnerabilidades

Resumen — últimos 7 días

Vulnerabilidades nuevas2884▼ 177 respecto a la semana anterior
Críticas / altas1281▼ 56 respecto a la semana anterior
Nueva explotación activa (KEV)5▼ 3 respecto a la semana anterior
Sin puntuar (sin CVSS)487▼ 22 respecto a la semana anterior
–

6 resultados, ordenados por fecha de publicación (más recientes primero)

CVEEstadoSeveridadEPSS Explotación activaTecnologías afectadasPublicada ▼Modificada Descripción
AplazadaMedia (4.3)0.14%—WP Accessibility HelperAI23/7/202623/7/2026
Unauthenticated Cross Site Request Forgery (CSRF) in WP Accessibility Helper (WAH) <= 0.6.6 versions.
AplazadaMedia (4.3)0.50%—Alex Volkov WP Accessibility HelperAI13/12/202417/6/2026
Missing Authorization vulnerability in Alex Volkov WP Accessibility Helper (WAH) allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Accessibility Helper (WAH): from n/a through 0.6.2.4.
AplazadaMedia (5.3)0.38%—Alex Volkov WP Accessibility HelperAI1/11/202417/6/2026
Missing Authorization vulnerability in Alex Volkov WP Accessibility Helper (WAH) allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WP Accessibility Helper (WAH): from n/a through 0.6.2.9.
AnalizadaMedia (4.3)0.26%—Volkov WP Accessibility Helper29/8/202417/6/2026
The WP Accessibility Helper (WAH) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'save_contrast_variations' and 'save_empty_contrast_variations' functions in all versions up to, and including, 0.6.2.8. This makes it possible for authenticated attackers,…
ModificadaAlta (8.8)0.32%—Volkov WP Accessibility Helper9/6/202417/6/2026
Missing Authorization vulnerability in Alex Volkov WP Accessibility Helper (WAH).This issue affects WP Accessibility Helper (WAH): from n/a through 0.6.2.5.
ModificadaMedia (6.1)1.7%—WP Accessibility Helper Project WP Accessibility Helper28/2/202217/6/2026
The WP Accessibility Helper (WAH) WordPress plugin before 0.6.0.7 does not sanitise and escape the wahi parameter before outputting back its base64 decode value in the page, leading to a Reflected Cross-Site Scripting issue