Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-12030: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in realmag777 MDTF – Meta Data and Taxonomies Filter

0
Medium
VulnerabilityCVE-2024-12030cvecve-2024-12030cwe-89
Published: Wed Jan 08 2025 (01/08/2025, 04:17:59 UTC)
Source: CVE Database V5
Vendor/Project: realmag777
Product: MDTF – Meta Data and Taxonomies Filter

Description

CVE-2024-12030 is a medium-severity SQL Injection vulnerability in the MDTF – Meta Data and Taxonomies Filter WordPress plugin, affecting all versions up to 1. 3. 3. 5. It arises from improper sanitization of the 'key' attribute in the 'mdf_value' shortcode, allowing authenticated users with Contributor-level access or higher to inject malicious SQL code. Exploitation does not require user interaction but does require authentication with limited privileges. Successful exploitation can lead to unauthorized disclosure of sensitive database information, impacting confidentiality but not integrity or availability. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or mitigating this vulnerability to prevent data leakage. Countries with significant WordPress usage and active contributor communities are at higher risk.

AI-Powered Analysis

AILast updated: 02/26/2026, 07:01:05 UTC

Technical Analysis

The vulnerability identified as CVE-2024-12030 affects the MDTF – Meta Data and Taxonomies Filter plugin for WordPress, specifically versions up to and including 1.3.3.5. The root cause is an SQL Injection flaw (CWE-89) stemming from insufficient escaping and lack of proper preparation of the SQL query that processes the 'key' attribute of the 'mdf_value' shortcode. Authenticated attackers with Contributor-level privileges or higher can exploit this flaw by injecting additional SQL commands into existing queries. This injection capability allows attackers to extract sensitive information from the backend database, such as user data or site configuration details, without requiring administrative privileges or user interaction. The vulnerability is remotely exploitable over the network (AV:N) with low attack complexity (AC:L), requiring only privileges of a Contributor or above (PR:L). The scope is unchanged (S:U), meaning the impact is confined to the vulnerable component. The confidentiality impact is high (C:H), while integrity and availability impacts are none (I:N, A:N). No patches have been linked yet, and no known exploits have been observed in the wild. The vulnerability was published on January 8, 2025, and assigned a CVSS v3.1 score of 6.5, indicating medium severity. The plugin is used in WordPress environments, which are widely deployed globally, making this a relevant threat to many organizations using this plugin for metadata and taxonomy filtering.

Potential Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive data stored in the WordPress database. Attackers with Contributor-level access can leverage this flaw to extract confidential information, potentially including user credentials, personal data, or site configuration details. While the vulnerability does not allow modification or deletion of data, the exposure of sensitive information can lead to further attacks such as privilege escalation, identity theft, or targeted phishing campaigns. Organizations relying on this plugin risk data breaches that could damage reputation, violate data protection regulations, and incur financial penalties. Since WordPress powers a significant portion of websites worldwide, especially small to medium enterprises and content-driven sites, the scope of impact is broad. The requirement for authenticated access limits exploitation to insiders or compromised accounts, but the low privilege level needed increases the risk. The absence of known exploits in the wild suggests limited active exploitation currently, but the vulnerability remains a significant risk until remediated.

Mitigation Recommendations

1. Immediate mitigation involves restricting Contributor-level and higher user privileges to trusted individuals only, minimizing the risk of exploitation from compromised accounts. 2. Monitor and audit Contributor and above user activities for suspicious behavior indicative of SQL injection attempts. 3. Apply strict input validation and sanitization on the 'key' attribute in the shortcode if custom code or temporary patches are feasible. 4. Disable or remove the MDTF plugin if it is not essential to reduce the attack surface until an official patch is released. 5. Maintain regular backups of the WordPress database to enable recovery in case of data compromise. 6. Follow vendor announcements closely and apply official patches or updates as soon as they become available. 7. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the vulnerable shortcode parameter. 8. Use principle of least privilege for all WordPress roles and consider implementing multi-factor authentication to reduce risk of account compromise. These steps go beyond generic advice by focusing on role-based access control, monitoring, and temporary protective measures specific to this plugin’s vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-12-02T15:19:50.332Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e2ab7ef31ef0b5970da

Added to database: 2/25/2026, 9:48:26 PM

Last enriched: 2/26/2026, 7:01:05 AM

Last updated: 2/26/2026, 9:20:39 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats