Wpmoose's vulnerability footprint centers on WordPress-related plugins and themes, particularly products such as Yuki and Kenta Blocks, with observed exposure clustered around web-application input-handling and authorization issues including cross-site request forgery, cross-site scripting, and missing authorization controls. Treat this as a compact vendor profile anchored to specific plugin/theme offerings; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Wpmoose over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-35731MEDIUM Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in WP Moose Kenta Gutenberg Blocks Responsive Blocks and block templates l | Jun 8, 2024 | 5.4 | 17 | NO | NO |
CVE-2024-1943MEDIUM The Yuki theme for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including 1.3.14. This is due to missing or incorrect nonce validation on the re | Feb 28, 2024 | 4.3 | 15 | NO | NO |
CVE-2024-1388MEDIUM The Yuki theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the reset_customizer_options() function in all versions up to, | Feb 28, 2024 | 4.3 | 14 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Wpmoose.
Media articles that mention a CVE ID that affects a product developed by Wpmoose — matched by CVE ID, not by vendor name.