Skip to main content

Flexible Chat CVE-2026-116861

| EUVDEUVD-2026-114312 HIGH
Insertion of Sensitive Information Into Sent Data (CWE-201)
2026-10-30 Patchstack GHSA-x75g-mwcv-7gf4
7.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach WordPress site over network
  2. Exploit
    Send unauthenticated request to Flexible Chat
  3. Impact
    Receive exposed sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Outbound data filtering
Exploitation Conditions

Exploitation requires only that a target run the WordPress 'Flexible Chat' plugin by wpdesk at version 1.1.0 or earlier and that it be network-reachable; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, no user interaction, and no special configuration are stated as prerequisites. The available sources do not specify which plugin feature, endpoint, or configuration triggers the disclosure or what sensitive data is returned, so any further conditions are not described in the evidence. The primary limiting factor is deployment footprint: only sites with this specific plugin installed at an affected version are exposed; there is no stated non-default-configuration or version-specific caveat beyond the <= 1.1.0 range.

Impact

The signals here are modest and internally consistent, which argues against treating this as an emergency despite the 7.5 'High' base score. The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a remotely reachable, low-complexity, unauthenticated flaw with high confidentiality impact but no integrity or availability impact (C:H/I:N/A:N) - i.e. a pure read/disclosure issue, not code execution or takeover. The vuln.today priority is 'this_week' rather than act_now or emergency, and the issue is NOT on the CISA KEV list, so there is no confirmed active exploitation. No EPSS probability was supplied, and no public exploit or PoC reference is present - the only reference is the Patchstack advisory itself, which is a vendor/database writeup, not working exploit code. So the picture is: a disclosure bug in a WordPress plugin, network-reachable without authentication, but with no evidence of exploitation in the wild and no known PoC. The main uncertainty is substantive: the description ('Unauthenticated Sensitive Data Exposure') and CWE-201 do not state WHAT data is exposed or HOW the flaw is triggered, so the real-world impact of C:H cannot be independently verified - if the exposed data is low-sensitivity, the practical risk is lower than the score implies. This is a real-but-bounded 'patch-this-week' disclosure issue rather than a widespread-exploitation priority.

Exploit ScenarioDerived

A remote attacker, without any authentication or user interaction, sends requests to a WordPress site running the Flexible Chat plugin at version 1.1.0 or earlier and receives sensitive information that should not be disclosed. No public exploit code or PoC is identified, and the exact data exposed and trigger mechanism are not described in the available sources. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, any such request would require no special positioning or privileges.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 30, 2026

Unauthenticated sensitive data exposure in the WordPress plugin Flexible Chat 1.1.0 and earlier allows network-reachable attackers to retrieve information the plugin should not expose, with a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). The affected footprint is limited to WordPress sites running the wpdesk plugin at or below version 1.1.0; the available sources do not specify the endpoint, parameter, or exact data returned, and no public exploit was identified at time of analysis. The priority signals are modest and internally consistent, so this should not be treated as an emergency despite the High base score.

RemediationAI

No vendor-released patch was identified at time of analysis, and the available sources do not list a fixed version. Consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/flexible-chat/vulnerability/wordpress-flexible-chat-plugin-1-1-0-sensitive-data-exposure-vulnerability?_s_id=cve for any update. Because the vulnerable endpoint is not described, the most directly supported compensating control is to deactivate the Flexible Chat plugin on sites that do not require it, accepting the loss of chat functionality; where the plugin must remain active, restrict access to the WordPress installation or its plugin endpoints at a reverse proxy or WAF to trusted networks, recognizing that this reduces exposure for reachable users but does not fix the underlying disclosure and may interfere with legitimate chat traffic.

Affected VersionsENISA

Flexible Chat n/a ≤1.1.0

Affected Packages

euvd flexible_chat no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Flexible Chat is a WordPress plugin published by wpdesk, identified in the affected CPE as cpe:2.3:a:wpdesk:flexible_chat. The flaw is classified as CWE-201, insertion of sensitive information into sent data, which means the plugin includes data in an outbound response that should not be exposed to the requester. The CVSS vector describes a network-reachable, low-complexity, unauthenticated issue with no user interaction and a high confidentiality impact, but the available sources do not identify the specific plugin feature, endpoint, request pattern, or data type involved, so the trigger is not described in the evidence. The practical exposure is bounded by deployment: only WordPress installations with this plugin present at version 1.1.0 or earlier are in scope.

Know when Flexible Chat gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Unauthenticated, network-reachable, low-complexity disclosure (AV:N/AC:L/PR:N/UI:N); confidentiality-only impact so I:N/A:N, C:H retained as the sources label it sensitive data though the exact data is unverified.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Unauthenticated Sensitive Data Exposure in Flexible Chat <= 1.1.0 versions.

Executive ViewAI

Why It Matters

The WordPress plugin Flexible Chat (versions 1.1.0 and earlier) contains a high-severity information disclosure flaw that could allow unauthenticated attackers to access sensitive data on affected sites. Any organization hosting WordPress with this plugin is exposed, and while no public exploit exists yet, leadership should prioritize remediation to prevent potential data leakage.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling the plugin, deploying WAF rules to block malicious requests, and restricting access to the affected endpoints.

Threat Intelligence Overview

EPSS Score
0.3%
Top 73% exploitable
Prevalence
Low
niche WordPress chat plugin, limited install base
Social Media
1
Sightings
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy