WordPress Medinik Core plugin <= 1.3.6 - SQL Injection vulnerability

The SQL Injection vulnerability in Medinik Core allows an attacker to bypass security measures and directly interact with the underlying database. Due to the 'blind' nature of the injection, attackers must infer data through multiple queries, making exploitation more time-consuming but still highly dangerous. Successful exploitation could lead to the exfiltration of sensitive user data, including usernames, passwords, email addresses, and potentially even financial information if the plugin handles e-commerce transactions. Lateral movement within the WordPress environment is also possible if the attacker can leverage the injected SQL to gain access to other plugins or themes. The blast radius extends to all users of websites utilizing the vulnerable Medinik Core plugin.

Websites using the Medinik Core plugin, particularly those handling sensitive user data or e-commerce transactions, are at significant risk. Shared hosting environments where multiple websites share the same database server are also at increased risk, as a compromise of one site could potentially lead to the compromise of others.

• wordpress / composer / npm:

grep -r "SELECT .* FROM" /var/www/html/wp-content/plugins/medinik-core/

• generic web:

curl -I https://example.com/medinik-core/vulnerable_endpoint.php?id=test' --header 'X-Custom-Header: SQL Injection Attempt'

• wordpress / composer / npm:

wp plugin list --status=inactive | grep medinik-core

1. 2026-02-20Disclosure

   disclosure

1. Gereserveerd2025-12-31
2. Gepubliceerd2026-02-20
3. Gewijzigd2026-04-28
4. EPSS bijgewerkt2026-03-23

The primary mitigation for CVE-2025-69307 is to upgrade to a patched version of the Medinik Core plugin as soon as it becomes available. Until a patch is released, consider implementing temporary workarounds. A Web Application Firewall (WAF) can be configured to filter potentially malicious SQL queries targeting the vulnerable endpoints. Specifically, rules should be created to block SQL injection attempts, focusing on common injection patterns. Additionally, restrict database user permissions to the minimum necessary for the plugin's functionality. After upgrade, confirm the vulnerability is resolved by attempting a controlled SQL injection test on the affected endpoint.