Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit unauthenticated crafted XSS message
-
DeliveryMessage stored in plugin database
-
ExploitPrivileged user opens message thread
-
ExecutionMalicious script executes in victim browser
-
PersistSession token exfiltrated to attacker server
-
ImpactAttacker replays token for admin access
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 | No authentication is required - the injection point is reachable by any unauthenticated visitor to the WordPress site (PR:N confirmed by CVSS vector). The critical limiting factor is UI:R: successful exploitation requires that a logged-in user (ideally one with elevated WordPress privileges such as an editor or administrator) actively views the attacker's submitted content, such as opening a message thread or accessing a message moderation queue. The plugin must be installed and active on the WordPress site. Exploitation is not constrained by any non-default configuration or special server-side setting based on available data. What limits impact: the attacker cannot trigger execution autonomously - they must wait for a victim to interact with the crafted content; and the C:L/I:L/A:L impact metrics cap the per-session impact, though privilege escalation via stolen admin cookies extends the realistic blast radius considerably. |
| Impact | The CVSS 7.1 score (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) reflects a meaningful real-world threat: the attack is network-reachable, requires no authentication, and has low complexity - only user interaction (UI:R) prevents a fully automated attack. The scope change elevates severity because XSS payloads running in an admin's browser can leverage that session context to perform privileged WordPress actions. No EPSS score was provided in the input data; without it, exploitation probability cannot be quantified precisely. The absence of a CISA KEV listing and no reported POC reduces immediate urgency compared to actively weaponized XSS vulnerabilities, but unauthenticated XSS in messaging plugins is a well-understood attack class frequently exploited in WordPress-targeting campaigns. The C:L/I:L/A:L impact ratings appear modestly scored relative to the potential for full admin compromise via session token theft - defenders should treat the realistic impact as higher than the individual metric values suggest if administrative users interact with attacker-submitted messages. |
| Exploit ScenarioDerived | An unauthenticated attacker visits the WordPress site, locates the BP Better Messages interface, and submits a message containing a crafted JavaScript payload (e.g., a script that exfiltrates document.cookie to an attacker-controlled endpoint). When a logged-in administrator or privileged user views or moderates that message in the WordPress dashboard or front-end messaging view, the script executes in their browser session, capturing their session cookie and transmitting it to the attacker. The attacker then replays the session token to gain administrative access to the WordPress site. No public proof-of-concept code has been identified, but this attack pattern requires no specialized tooling beyond a browser. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 18, 2026
Unauthenticated Cross-Site Scripting (XSS) in the BP Better Messages WordPress plugin versions up to and including 2.15.22 allows remote unauthenticated attackers to inject malicious scripts that execute in the browser of any user who views attacker-controlled content. The scope-changed CVSS vector (S:C) indicates the injected script can operate beyond the plugin's context, enabling session hijacking, credential theft, or admin account takeover when a privileged user views the payload. No public exploit code or CISA KEV listing has been identified at time of analysis, though the unauthenticated attack vector and low complexity lower the barrier significantly for opportunistic exploitation.
RemediationAI
Update BP Better Messages to a version beyond 2.15.22 immediately - patch availability per vendor advisory is indicated by the Patchstack report at https://patchstack.com/database/wordpress/plugin/bp-better-messages/vulnerability/wordpress-bp-better-messages-plugin-2-15-22-cross-site-scripting-xss-vulnerability, though the exact patched release version was not independently confirmed in the available input data. Until patching is complete, consider temporarily disabling the BP Better Messages plugin on sites where administrative or privileged users regularly view community-submitted messages, accepting the trade-off of lost messaging functionality. Deploying a Web Application Firewall (WAF) rule targeting XSS patterns in plugin-specific request parameters can serve as a compensating control but should not substitute for patching. Restrict who can submit messages to authenticated-only users as a partial mitigation, reducing the unauthenticated attack surface at the cost of limiting open community engagement.
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
BP Better Messages (CPE: cpe:2.3:a:wordplus:bp_better_messages:*:*:*:*:*:*:*:*) is a messaging plugin for WordPress/BuddyPress environments, enabling direct messaging and group chat on community sites. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), meaning the plugin fails to sanitize or encode attacker-supplied input before rendering it in the browser. Because the CVSS vector specifies PR:N, the injection point is accessible without authentication - likely a message submission, contact form field, or chat input that is then rendered to other users. The S:C (scope changed) designation confirms the injected script executes in a security context beyond the plugin's own origin boundary, typical of stored or reflected XSS that runs in the victim's browser session where higher-privilege tokens exist.
Know when Bp Better Messages 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:R/S:C/C:L/I:L/A:L
XSS via unauthenticated message submission; scope changes to victim browser (S:C), but no direct availability impact is described.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in BP Better Messages <= 2.15.22 versions.
Executive ViewAI
BP Better Messages WordPress plugin (versions 2.15.22 and earlier) contains an unauthenticated Cross-Site Scripting vulnerability that allows attackers to inject malicious code executed in any user's browser, creating direct risk of administrator account compromise and credential theft. When privileged users view attacker-controlled content, injected scripts operate outside the plugin's context and can facilitate session hijacking and account takeover. Organizations running this plugin require immediate mitigation to prevent privilege escalation attacks.
Disable and deactivate the BP Better Messages plugin. For installations where removal is not feasible: restrict WordPress administrator access to specific IP addresses and corporate VPN only; implement Content Security Policy HTTP headers to prevent unauthorized script execution; deploy WAF rules to detect and block XSS payloads targeting the plugin; enforce multi-factor authentication for all WordPress administrator and editor accounts; conduct weekly audits of WordPress access and plugin activity logs; and provide security awareness training to users on the risks of clicking untrusted links or viewing content from unknown sources.
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 Bp Better Messages
View allDOM-based cross-site scripting in the BuddyPress-dependent BP Better Messages WordPress plugin affects versions through
Cross-site scripting in the BP Better Messages WordPress plugin (≤2.15.27) allows unauthenticated remote attackers to in
EUVD-2026-60910
GHSA-w8j9-g92x-3rcc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB