CVE-2026-14189: WPBot admin-set field IDs

CISO Take

WPBot, a WordPress chatbot/search plugin, fails to validate administrator-configured field identifiers before splicing them into a SQL query, so a malicious or compromised admin account can plant an injection that fires whenever an ordinary site visitor runs a search. There's no CVSS score, no EPSS data, no CISA KEV listing, and no public exploit or scanner template for this CVE, so it isn't being mass-exploited today — but privileges required are already administrator-level, meaning the real exposure is a compromised or rogue admin account turning every visitor search into a database-exfiltration or corruption vector. WPBot's package risk score is 0/100 with no dependent or health data available, so treat it as an unmaintained-adjacent WordPress plugin rather than a hardened chatbot backend. Patch to WPBot 8.5.2 or later now; until then, enforce MFA and least-privilege on all WordPress admin accounts, audit WPBot's search field configuration for anomalous SQL syntax, and add WAF rules to catch injection patterns on the front-end search endpoint.

Sources: NVD

What is the risk?

Practical exploitation risk is currently low-to-moderate: the flaw requires administrator access to plant, and there is no CVSS score, EPSS percentile, KEV listing, public exploit, or Nuclei template to suggest active or imminent mass exploitation. However, the impact model is asymmetric — a single compromised/malicious admin credential converts into a persistent, unauthenticated attack surface against every visitor who uses the site's search feature, which is a classic second-order/stored SQLi pattern. Given WPBot's unscored package health (0/100 risk score, no dependent data), this should be prioritized as a routine-but-not-urgent patch, with heightened urgency for any site where admin account hygiene (shared logins, no MFA) is weak.

How does the attack unfold?

Initial Access

Attacker obtains or abuses WordPress administrator-level access (compromised credentials, insider, or chained privilege escalation).

Malicious Configuration

Attacker sets a WPBot search field identifier containing crafted SQL injection payload instead of a valid field name.

Trigger by Visitor

An unauthenticated site visitor performs a search via the WPBot widget, causing the malicious field identifier to be interpolated into a live SQL query.

AML.T0049

Impact

The injected SQL executes against the WordPress database, enabling data exfiltration or corruption without further attacker interaction.

Initial Access

Attacker obtains or abuses WordPress administrator-level access (compromised credentials, insider, or chained privilege escalation).

Malicious Configuration

Attacker sets a WPBot search field identifier containing crafted SQL injection payload instead of a valid field name.

Trigger by Visitor

An unauthenticated site visitor performs a search via the WPBot widget, causing the malicious field identifier to be interpolated into a live SQL query.

AML.T0049

Impact

The injected SQL executes against the WordPress database, enabling data exfiltration or corruption without further attacker interaction.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
WPBot	pip	—	No patch

Do you use WPBot? You're affected.

How severe is it?

CVSS 3.1

N/A

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

Trivial

What should I do?

1 step

1) Upgrade WPBot to version 8.5.2 or later immediately. 2) Until patched, enforce MFA and least-privilege access on all WordPress administrator accounts, since exploitation requires admin-level configuration access. 3) Audit existing WPBot search field identifier configurations for unexpected SQL syntax (UNION, stacked queries, comment sequences). 4) Add WAF/reverse-proxy rules to flag anomalous payloads reaching the WPBot search endpoint from unauthenticated visitors. 5) Monitor database query logs for unexpected query shapes originating from the plugin's search handler.

How is it classified?

Data Leakage Code Execution Plugin Agent AML.T0049 - Exploit Public-Facing Application

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.6.2.3 - Third-party and supplier management for AI system components

OWASP LLM Top 10

LLM06 - Sensitive Information Disclosure

Frequently Asked Questions

What is CVE-2026-14189?

WPBot, a WordPress chatbot/search plugin, fails to validate administrator-configured field identifiers before splicing them into a SQL query, so a malicious or compromised admin account can plant an injection that fires whenever an ordinary site visitor runs a search. There's no CVSS score, no EPSS data, no CISA KEV listing, and no public exploit or scanner template for this CVE, so it isn't being mass-exploited today — but privileges required are already administrator-level, meaning the real exposure is a compromised or rogue admin account turning every visitor search into a database-exfiltration or corruption vector. WPBot's package risk score is 0/100 with no dependent or health data available, so treat it as an unmaintained-adjacent WordPress plugin rather than a hardened chatbot backend. Patch to WPBot 8.5.2 or later now; until then, enforce MFA and least-privilege on all WordPress admin accounts, audit WPBot's search field configuration for anomalous SQL syntax, and add WAF rules to catch injection patterns on the front-end search endpoint.

Is CVE-2026-14189 actively exploited?

No confirmed active exploitation of CVE-2026-14189 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-14189?

1) Upgrade WPBot to version 8.5.2 or later immediately. 2) Until patched, enforce MFA and least-privilege access on all WordPress administrator accounts, since exploitation requires admin-level configuration access. 3) Audit existing WPBot search field identifier configurations for unexpected SQL syntax (UNION, stacked queries, comment sequences). 4) Add WAF/reverse-proxy rules to flag anomalous payloads reaching the WPBot search endpoint from unauthenticated visitors. 5) Monitor database query logs for unexpected query shapes originating from the plugin's search handler.

What systems are affected by CVE-2026-14189?

This vulnerability affects the following AI/ML architecture patterns: agent frameworks.

What is the CVSS score for CVE-2026-14189?

No CVSS score has been assigned yet.

What is the AI security impact?

Affected AI Architectures

agent frameworks

MITRE ATLAS Techniques

AML.T0049 Exploit Public-Facing Application

Compliance Controls Affected

ISO 42001: A.6.2.3

OWASP LLM Top 10: LLM06

What are the technical details?

Original Advisory

The WPBot WordPress plugin before 8.5.2 does not validate administrator-configured field identifiers before using them in a SQL query, allowing users with administrator access to perform SQL injection that executes when a visitor triggers a search.

Exploitation Scenario

A malicious insider or an attacker who has already compromised a WordPress administrator account (via credential stuffing, phishing, or a separate privilege-escalation bug) configures a WPBot search field identifier containing injected SQL syntax instead of a legitimate field name. The payload lies dormant in the plugin configuration until an unauthenticated site visitor triggers the chatbot's search feature, at which point the injected SQL executes against the WordPress database — potentially exfiltrating user credentials/PII or corrupting stored data, all without the visitor's knowledge and without further attacker interaction.