CVE-2024-12103
Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure
Vexday Risk Score
13Bajo
Decisión SSVC (CISA)
Track
Sin señal de explotación → monitorear
CVSS 5.3EPSS 0.4%KEV nãoPoC —Nuclei —Metasploit —Patch —
Ciclo de vida
24 dic 2024Publicada en NVD
Recomendación: Monitorear — sin señal de explotación por ahora.
The Content No Cache: prevent specific content from being cached plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 0.1.2 via the eos_dyn_get_content action due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Productos afectados
giuse · Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.¿Quieres saber si tu infraestructura está expuesta a esto?
Hablar con TrueHacking →