Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain public token-shared board link
-
DeliverySend unauthenticated request for member data
-
ExploitServer returns unrestricted member records
-
ExecutionHarvest member/administrator email addresses
-
ImpactUse emails for targeted phishing
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a FluentBoards board has been shared via the plugin's public, token-shared board feature; against such a shared board, an unauthenticated remote attacker can request member data and receive the members' email addresses (typically including administrators). The limiting factor is that only boards actively exposed through public token sharing are affected - boards that are not publicly shared do not leak data - so the realistic attack surface is confined to sites using the share-link feature on FluentBoards versions 1.95 through before 2.1.0. No authentication, user interaction, or non-default server settings beyond enabling board sharing are needed. |
| Impact | All signals point to a genuine but low-to-moderate priority information-disclosure issue rather than a critical exposure. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3) is internally consistent with the description: a network-reachable, unauthenticated, low-complexity read of member email addresses, with only confidentiality impact (C:L) and no integrity or availability effect. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no evidence of active or automated exploitation - this is a targeted-value leak (harvesting admin/member emails for phishing or credential-stuffing target lists), not a widespread mass-exploitation candidate. The one caveat limiting real-world exposure is that the leak only occurs through the plugin's public token-shared board feature, meaning a board must actually be shared via a public token link for the disclosure to trigger; that gate is not reflected in the AC:L rating but materially narrows the affected population. No conflicting signals across sources: WPScan (reporter), NVD, and EUVD agree on scope and the 5.3 rating. |
| Exploit ScenarioDerived | An attacker discovers or is given a FluentBoards public token-share link for a board and requests the shared board's member data without authenticating; the response includes the email addresses of the board's members, which typically include the site's administrators. The attacker uses the harvested admin emails to craft targeted phishing or credential-stuffing attacks. No public exploit code is identified at time of analysis, and exploitation requires low complexity once a shared-board token/link is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Unauthenticated information disclosure in the FluentBoards WordPress plugin (versions 1.95 through before 2.1.0) lets remote attackers retrieve the email addresses of a shared board's members - typically including site administrators - by querying the plugin's public, token-shared board endpoint. Exploitation requires only that a board has been exposed via the plugin's share-link feature; no credentials or user interaction are needed, consistent with the CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector and a confidentiality-only impact (C:L). No public exploit code has been identified and the issue is not confirmed as actively exploited (not in CISA KEV), but the low EPSS-relevant barrier and the administrative-email exposure make it a useful reconnaissance primitive for follow-on phishing or credential attacks against FluentBoards sites that use public board sharing.
RemediationAI
Vendor-released patch: upgrade FluentBoards to version 2.1.0 or later - 2.1.0 is the first release that properly restricts member data returned by the public token-shared board feature, and it closes the disclosure path identified by WPScan. Until the upgrade can be staged, the most effective compensating control is to disable public board sharing entirely (remove or leave unused the plugin's share-link/public board capability) and to revoke or regenerate any existing share tokens, accepting that legitimate external stakeholders will lose anonymous board access and must instead be given authenticated WordPress accounts with appropriate roles. If public sharing must remain for business reasons, treat every shared board URL as a public artifact: remove administrator and privileged accounts from shared boards' member lists, avoid using project members whose email addresses are sensitive, and place an edge/WAF rule or CDN cache-bypass in front of the shared-board endpoint so leaked member responses are not stored by intermediaries - noting this reduces but does not eliminate exposure because the endpoint itself still returns the data. After patching, confirm the plugin version in wp-admin/plugin list and, if a cache or CDN fronts the site, purge cached responses for previously public share URLs. Reference advisories: https://wpscan.com/vulnerability/d1aaacdf-7427-411f-b376-999793524a4b/ and https://nvd.nist.gov/vuln/detail/CVE-2026-89331.
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
FluentBoards is a WordPress project/kanban management plugin whose 'public, token-shared board' feature exposes a board to anyone holding a share token, without requiring a WordPress account. The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): the member-data response returned by that shared-board endpoint is not properly restricted, so the serialization/response layer emits member records - including email addresses - to unauthenticated callers instead of limiting output to non-sensitive display fields (name, avatar, role label). There is no authorization check failure in the classic sense (the share token is valid by design); the flaw is that the data projection over that trusted-but-public context is over-broad. CPE/version data place the affected range at FluentBoards 1.95 up to, but not including, 2.1.0, meaning earlier 1.x releases may not contain the vulnerable public-share member endpoint at all, and 2.1.0 restores proper field restriction. Because the leak occurs on a public endpoint with no authentication, caching layers or CDNs in front of WordPress can also retain the leaked responses.
Know when WordPress 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:L/I:N/A:N
Unauthenticated network read (PR:N/AV:N/AC:L) limited to disclosure of member email addresses, so C:L with no integrity or availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The FluentBoards WordPress plugin before 2.1.0 does not properly restrict the member data returned by its public, token-shared board feature, allowing unauthenticated users to disclose the email addresses of a shared board's members, typically including administrators.
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.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-85053
GHSA-g2qq-c2w5-46xc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB