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-14719: CWE-89 SQL Injection in Relevanssi

0
Medium
VulnerabilityCVE-2025-14719cvecve-2025-14719cwe-89
Published: Wed Jan 07 2026 (01/07/2026, 06:00:09 UTC)
Source: CVE Database V5
Product: Relevanssi

Description

CVE-2025-14719 is a medium severity SQL Injection vulnerability in the Relevanssi WordPress plugin versions before 4. 26. 0 and Relevanssi Premium before 2. 29. 0. It allows users with contributor or higher roles to inject malicious SQL code due to improper sanitization and escaping of input parameters. The vulnerability does not require user interaction but does require authenticated access with elevated privileges. Exploitation can lead to unauthorized disclosure of sensitive data, impacting confidentiality without affecting integrity or availability. No known exploits are currently reported in the wild. European organizations using vulnerable versions of Relevanssi are at risk, especially those with contributors who have elevated WordPress roles.

AI-Powered Analysis

AILast updated: 01/14/2026, 15:44:42 UTC

Technical Analysis

CVE-2025-14719 identifies a SQL Injection vulnerability in the Relevanssi WordPress plugin, specifically affecting versions prior to 4.26.0 and Relevanssi Premium versions before 2.29.0. The root cause is the failure to properly sanitize and escape a parameter before incorporating it into an SQL query. This flaw allows authenticated users with contributor or higher roles to craft malicious input that alters the intended SQL command, potentially exposing sensitive database information. The vulnerability requires no user interaction but does require authenticated access with elevated privileges, limiting the attack surface to users who already have some level of trust within the WordPress environment. The CVSS score of 4.9 reflects a medium severity, primarily due to the need for authenticated access and the impact being limited to confidentiality breaches without affecting data integrity or availability. No public exploits have been reported, but the vulnerability poses a risk to websites relying on Relevanssi for search functionality, especially those with multiple contributors. The plugin is widely used for enhancing WordPress search capabilities, making this a relevant concern for content-heavy sites. The vulnerability was reserved in December 2025 and published in January 2026, indicating recent discovery and disclosure. The lack of patch links suggests that users should monitor official channels for updates or apply manual mitigations.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive information stored in WordPress databases, including user data, content drafts, or configuration details. Since contributors and above roles can exploit this flaw, organizations with collaborative content creation workflows are particularly vulnerable. The breach of confidentiality could result in data privacy violations under GDPR, leading to regulatory penalties and reputational damage. Although the vulnerability does not affect data integrity or availability, the exposure of sensitive information can facilitate further attacks or social engineering campaigns. The medium severity rating reflects a moderate risk, but the impact can be significant for organizations managing sensitive or regulated data. Additionally, the exploitation requires authenticated access, so insider threats or compromised contributor accounts increase risk. European companies using Relevanssi in sectors such as media, education, government, and e-commerce should prioritize addressing this vulnerability to maintain compliance and protect user trust.

Mitigation Recommendations

1. Immediately update the Relevanssi plugin to version 4.26.0 or later, and Relevanssi Premium to version 2.29.0 or later once available. 2. Until patches are applied, restrict contributor and higher roles to trusted users only, minimizing the risk of exploitation from compromised accounts. 3. Implement strict role-based access controls and monitor contributor activities for unusual behavior. 4. Employ Web Application Firewalls (WAFs) with SQL Injection detection rules tailored to WordPress environments to block suspicious queries. 5. Regularly audit WordPress plugins for updates and security advisories, integrating automated vulnerability scanning into the development and deployment pipelines. 6. Consider disabling or limiting the use of Relevanssi search functionality if it is not critical, reducing the attack surface. 7. Backup WordPress databases frequently and securely to enable recovery in case of compromise. 8. Educate content contributors about phishing and credential security to prevent account takeover. 9. Monitor logs for anomalous SQL queries or access patterns indicative of exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2025-12-15T13:56:37.853Z
Cvss Version
null
State
PUBLISHED

Threat ID: 695dfb8aa55ed4ed99834207

Added to database: 1/7/2026, 6:22:02 AM

Last enriched: 1/14/2026, 3:44:42 PM

Last updated: 2/7/2026, 10:42:23 AM

Views: 48

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