Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister subscriber account on target site
-
DeliverySet display name to entity-encoded XSS payload
-
ExploitPayload stored, bypassing sanitize_text_field()
-
ExecutionVictim views page rendering display name
-
PersistPlugin decodes and injects script
-
ImpactArbitrary JS runs in victim browser context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the Better Messages plugin (<=3.0.4) installed and active on a WordPress site, plus the attacker holding at least a subscriber-level account - so sites permitting open/self-service registration are most exposed, while sites restricting account creation limit reach. The core enabling condition is that the display-name value is processed only by sanitize_text_field(), which preserves HTML-entity-encoded content, and the plugin then decodes it server-side before output; this specific decode-after-sanitize behavior is what lets low-privilege users bypass the normal unfiltered_html capability gate. No victim interaction beyond viewing a page that renders the attacker's display name is needed, and no non-default plugin configuration is required. |
| Impact | This is a mid-severity, authentication-gated stored/DOM XSS with a realistic but bounded threat profile. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) indicates a remotely-reachable, low-complexity attack that requires only subscriber-level authentication (PR:L) and, notably, NO victim interaction beyond normal browsing (UI:N) - any user who views a page rendering the malicious display name executes the payload. The scope-change (S:C) reflects that the injected script runs in other users' browser contexts. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence, so per available data this is 'no public exploit identified at time of analysis.' The interesting technical signal is the described sanitization bypass: WordPress core's sanitize_text_field() preserves HTML-entity-encoded payloads, and the plugin decodes them server-side before output - meaning the standard unfiltered_html capability restriction that normally protects low-privilege users is defeated. That elevates real-world plausibility above a typical 'requires trusted author' XSS. Net: a genuine issue worth patching promptly on affected sites that allow open/subscriber registration, but absent EPSS/KEV/POC signals it is not an emergency-tier, mass-exploited flaw. Impact is limited to C:L/I:L (session/context compromise of viewers), not full site takeover. |
| Exploit ScenarioDerived | An attacker registers a subscriber-level account (or uses any low-privilege account) on a WordPress site running Better Messages and sets their display name to an HTML-entity-encoded XSS payload (e.g., an iframe srcdoc attribute) that survives sanitize_text_field(). The plugin later decodes and renders the display name in chat/message UI, so any user - including administrators - who views a page showing that name has arbitrary JavaScript executed in their browser session. No public exploit code was identified in the provided intelligence, but the bypass technique is described in detail by the Wordfence advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Stored DOM-based cross-site scripting in the Better Messages WordPress plugin (all versions up to and including 3.0.4) lets any authenticated subscriber-level user persist arbitrary script through their WordPress display name, which then executes in the browser of anyone who views a page that renders that name. Because the value is only run through sanitize_text_field() and the plugin subsequently decodes it server-side before rendering, a low-privilege account bypasses the normal unfiltered_html capability gate, and no victim interaction beyond page view is required. Rated CVSS 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), this is a mid-severity, authentication-gated issue with a realistic but bounded threat profile, most dangerous on sites that permit open or self-service registration; no public exploit identified at time of analysis.
RemediationAI
Upgrade the Better Messages plugin to 3.0.5, the version referenced by the project's Trac changeset (which updates the affected BuddyBoss addon file from tags/3.0.3 to tags/3.0.5); this removes the decode-after-sanitize behavior that lets entity-encoded display names become executable markup. If an immediate upgrade is not possible, the most effective compensating control is to close the exposure window for low-privilege accounts: disable open/self-service user registration or require administrator approval for new accounts, with the trade-off that legitimate onboarding is throttled and existing subscriber accounts remain a residual risk. A WAF or virtual patch rule that rejects HTML-entity-encoded markup (for example payloads containing <iframe or srcdoc fragments) in profile/display-name submission endpoints can block the delivery vector, but it must be tuned carefully to avoid breaking legitimate names containing special characters. As a last resort, a child-theme or site-specific filter that strips or re-encodes display names before they are rendered in chat surfaces can neutralize the sink, though this is a temporary measure and may suppress legitimate formatting. Because the underlying defect is the server-side decode of sanitized input, patching to 3.0.5 remains strongly preferred over any workaround. Additional detail is in the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/f4f5a268-7e7f-4dbe-823a-a17ac0f52928?source=cve.
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
The flaw is a classic Cross-Site Scripting class issue (CWE-79) manifesting as stored, DOM-based XSS in a WordPress plugin from vendor WordPlus (CPE cpe:2.3:a:wordplus:better_messages_-_chat_rooms,_group_chat,_private_messages_&_ai_chat_bots). WordPress core's sanitize_text_field() strips tags but deliberately preserves HTML-entity-encoded content, so a payload such as an entity-encoded iframe srcdoc attribute survives the sanitization step and can be stored as a user's display name without the unfiltered_html capability that subscribers normally lack. The plugin then performs an html_entity_decode-style transformation server-side before writing the value into the rendered page, which reconstitutes the markup and lets it be interpreted by the browser in the context of the page - that decode-after-sanitize ordering is the root cause. The referenced Trac source lines (inc/functions.php lines 1117 and 2276 in tag 3.0.3) and the BuddyBoss addon changeset between tags 3.0.3 and 3.0.5 point to the affected code path in the plugin's display-name handling, which is relevant wherever the plugin surfaces usernames in chat rooms, group chats, private messages, or AI chat bot interfaces (including BuddyPress/BuddyBoss-integrated sites).
Know when Wordpress Plugin 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:L/UI:N/S:C/C:L/I:L/A:N
Network-reachable, low-complexity injection needing only subscriber auth (PR:L); no victim interaction (UI:N); scope changes as script runs in other users' browsers (S:C) with limited C/I impact, no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Better Messages - Chat Rooms, Group Chat, Private Messages & AI Chat Bots plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via User Display Name in all versions up to, and including, 3.0.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by Subscriber-level users because WordPress core's sanitize_text_field() preserves HTML-entity-encoded payloads (e.g., an iframe srcdoc attribute), allowing the encoded string to be stored as a display name without requiring the unfiltered_html capability, and the plugin subsequently decodes it server-side before rendering.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe 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 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
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-86549
GHSA-5vv2-wcc7-jmpm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB