Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach WordPress site over network
-
ExploitSend unauthenticated request to Flexible Chat
-
ImpactReceive 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Sensitive Data Exposure in Flexible Chat <= 1.1.0 versions.
Executive ViewAI
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-114312
GHSA-x75g-mwcv-7gf4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB