Block Logic <= 1.0.8 - Authenticated (Contributor+) Remote Code Execution

Successful exploitation of CVE-2025-2303 allows an attacker to gain complete control over the WordPress server. Given the plugin's functionality, an attacker could modify website content, install malicious plugins, steal sensitive data (user credentials, database information), and potentially pivot to other systems on the network. The impact is particularly severe because the vulnerability requires only Contributor-level access, a relatively low privilege level within WordPress, making it easier for attackers to exploit. This vulnerability shares similarities with other code execution flaws in WordPress plugins where user input is not properly sanitized before being used in code execution functions.

Websites using the Block Logic – Full Gutenberg Block Display Control plugin, particularly those with multiple contributors or users with elevated privileges, are at significant risk. Shared hosting environments where multiple WordPress sites share the same server are also at increased risk, as a compromise on one site could potentially lead to compromise of others.

• wordpress / plugin:

wp plugin list | grep 'Block Logic – Full Gutenberg Block Display Control'

• wordpress / plugin: Check plugin version in WordPress admin dashboard. • wordpress / plugin: Review WordPress access logs for suspicious requests targeting the blocklogiccheck_logic function. • wordpress / plugin: Use wp-cli to check for vulnerable plugin versions: wp plugin update --all (and review output for updates). • wordpress / plugin: Monitor WordPress security plugin alerts for CVE-2025-2303.

1. 2025-03-22Disclosure

   disclosure

2. 2025-03-22Patch

   patch

1. Reserviert2025-03-14
2. Veröffentlicht2025-03-22
3. Geändert2026-04-08
4. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2025-2303 is to immediately upgrade the Block Logic – Full Gutenberg Block Display Control plugin to version 2.0.0 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider temporarily restricting access to the plugin's settings or disabling the plugin entirely. While not a complete solution, a Web Application Firewall (WAF) configured to block requests containing suspicious input to the blocklogiccheck_logic function might offer some protection. After upgrading, verify the fix by attempting to trigger the vulnerable function with malicious input and confirming that it is properly sanitized and does not result in code execution.

Aktive Installationen

300Nische

Plugin-Bewertung