Vulnerabilities (CVE)

Filtered by vendor Dotcamp Subscribe
Filtered by product Ultimate Blocks
Total 5 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-4655 1 Dotcamp 1 Ultimate Blocks 2024-11-21 N/A 5.4 MEDIUM
The Ultimate Blocks WordPress plugin before 3.1.9 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks
CVE-2024-4268 1 Dotcamp 1 Ultimate Blocks 2024-11-21 N/A 6.4 MEDIUM
The Ultimate Blocks – WordPress Blocks Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's blocks in all versions up to, and including, 3.1.9 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVE-2024-3513 1 Dotcamp 1 Ultimate Blocks 2024-11-21 N/A 6.4 MEDIUM
The Ultimate Blocks – WordPress Blocks Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the title tag parameter in all versions up to, and including, 3.1.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access and higher, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVE-2024-37457 1 Dotcamp 1 Ultimate Blocks 2024-11-21 N/A 6.5 MEDIUM
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Ultimate Blocks Ultimate Blocks – Gutenberg Blocks Plugin allows Stored XSS.This issue affects Ultimate Blocks – Gutenberg Blocks Plugin: from n/a through 3.1.9.
CVE-2024-8536 1 Dotcamp 1 Ultimate Blocks 2024-10-03 N/A 5.4 MEDIUM
The Ultimate Blocks WordPress plugin before 3.2.2 does not validate and escape some of its block attributes before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks