CVE-2025-14719VulnerabilityPublished 7 Jan 2026

CVE-2025-14719: Relevanssi (WordPress plugin) · SQL Injection

Affects Relevanssi (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 4.9 Medium : upgrade to 4.26.0 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.26.0, 2.29.0

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Relevanssi to 4.26.0; Relevanssi Premium to 2.29.0.

Affected software

Product	Affected	Fixed in
Relevanssi	Affected <4.26.0	Fixed in 4.26.0
Relevanssi Premium	Affected <2.29.0	Fixed in 2.29.0

AI-suggested

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. If you cannot patch yet, 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.

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.

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.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/bd8e27c7-8f97-4313-b16e-50ac6f0676f5/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 15:44 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats