Skip to main content
CVE-2026-115224VulnerabilityPublished

The Customer Engagement System WordPress plugin before 2.0.2 does not safely build the SQL statements that store a

Source GCVE Database

0
Authoritative record:CVE-2026-115224· High

Not known to be exploited : upgrade to 2.0.2 soon.

Data as of 28 Oct 2026, 07:14 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 2.0.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Customer Engagement System (WordPress plugin) to 2.0.2.

Affected software

ProductAffectedFixed in
Customer Engagement SystemAffected
  • <2.0.2
Fixed in
  • 2.0.2

AI-suggested

Upgrade the Customer Engagement System WordPress plugin to version 2.0.2 or later, where this SQL injection vulnerability has been fixed.

Description

The Customer Engagement System WordPress plugin versions before 2.0.2 contain a SQL injection vulnerability. This flaw arises because the plugin does not safely construct SQL statements for storing popup visibility rules, directly concatenating user-supplied ID values into an INSERT query without parameter binding or integer casting. An authenticated administrator can exploit this to inject arbitrary SQL and read the WordPress database contents.

References

Community reviews

Loading reviews…