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-2025-14973: CWE-89 SQL Injection in Recipe Card Blocks Lite

0
Medium
VulnerabilityCVE-2025-14973cvecve-2025-14973cwe-89
Published: Mon Jan 26 2026 (01/26/2026, 06:00:13 UTC)
Source: CVE Database V5
Product: Recipe Card Blocks Lite

Description

CVE-2025-14973 is a medium severity SQL injection vulnerability in the Recipe Card Blocks Lite WordPress plugin versions before 3. 4. 13. It allows users with contributor-level or higher privileges to inject malicious SQL code due to improper sanitization and escaping of input parameters. The vulnerability can lead to unauthorized disclosure of sensitive data but does not affect data integrity or availability. Exploitation requires authenticated access with elevated privileges but no user interaction beyond that. No known exploits are currently reported in the wild. European organizations using this plugin on WordPress sites should prioritize updating to version 3. 4. 13 or later to mitigate risk.

AI-Powered Analysis

AILast updated: 02/02/2026, 08:43:23 UTC

Technical Analysis

CVE-2025-14973 is a SQL injection vulnerability identified in the Recipe Card Blocks Lite WordPress plugin, specifically in versions prior to 3.4.13. The root cause is the plugin's failure to properly sanitize and escape a parameter before incorporating it into an SQL query. This flaw allows users with contributor-level privileges or higher to craft malicious input that alters the intended SQL command, potentially exposing sensitive database information. The vulnerability affects the confidentiality of data but does not impact integrity or availability, as the CVSS vector indicates no integrity or availability loss. The attack vector is network-based (AV:N), with low attack complexity (AC:L), but requires privileges (PR:H) and no user interaction (UI:N). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. Although no public exploits are currently known, the presence of this vulnerability in a widely used WordPress plugin poses a significant risk if left unpatched. The plugin is commonly used to display recipe cards on WordPress sites, which may contain user-generated content, making it a target for attackers seeking to extract database information. The vulnerability was reserved in December 2025 and published in January 2026, with a CVSS score of 6.8, categorized as medium severity.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive data stored within WordPress databases, including user information, content, and potentially credentials if stored insecurely. Since exploitation requires contributor-level access, the risk is higher in environments where multiple users have elevated privileges or where account compromise is possible. The confidentiality breach could damage organizational reputation, violate data protection regulations such as GDPR, and lead to compliance penalties. Although the vulnerability does not allow data modification or service disruption, the exposure of sensitive data is critical, especially for organizations handling personal or proprietary information. Websites relying on Recipe Card Blocks Lite for content presentation, particularly in sectors like food blogging, e-commerce, or hospitality, may be targeted. The medium severity rating suggests a moderate but actionable risk, emphasizing the need for timely patching to prevent potential exploitation.

Mitigation Recommendations

European organizations should immediately update the Recipe Card Blocks Lite plugin to version 3.4.13 or later, where the vulnerability is fixed. Until the update is applied, restrict contributor and higher privileges to trusted users only and audit existing user roles to minimize exposure. Implement Web Application Firewalls (WAFs) with SQL injection detection rules tailored to WordPress environments to provide an additional layer of defense. Regularly monitor WordPress logs for unusual database query patterns or access attempts indicative of exploitation attempts. Employ the principle of least privilege for WordPress user roles and consider multi-factor authentication to reduce the risk of account compromise. Conduct security awareness training for content contributors to recognize phishing or social engineering attempts that could lead to privilege escalation. Finally, maintain regular backups of WordPress databases and files to enable recovery in case of an incident.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2025-12-19T15:07:18.554Z
Cvss Version
null
State
PUBLISHED

Threat ID: 697707c94623b1157c67230a

Added to database: 1/26/2026, 6:20:57 AM

Last enriched: 2/2/2026, 8:43:23 AM

Last updated: 2/7/2026, 8:01:42 AM

Views: 37

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