dbcve.org
Better MessagesWordPress extension · Wordplus

CVE-2023-49168

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 2.4.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WordPlus Better Messages – Live Chat for WordPress, BuddyPress, PeepSo, Ultimate Member, BuddyBoss allows Stored XSS.This issue affects Better Messages – Live Chat for WordPress, BuddyPress, PeepSo, Ultimate Member, BuddyBoss: from n/a through 2.4.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored Cross-Site Scripting (XSS) vulnerability in the WordPress plugin Better Messages (versions through 2.4.0) allows authenticated users to inject malicious JavaScript through chat messages or user inputs that are not properly sanitized before being displayed to other users, leading to script execution in victims' browsers.

MitigationUpgrade to version 2.4.0 or later if a patched version is available; otherwise, implement proper input sanitization (sanitize_text_field, wp_kses) and output escaping (esc_html, esc_attr) on all user-generated content display points within the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Better MessagesWordPress extension
Affected:< 2.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Better Messages plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Better Messages' by Wordplus in the list
    Affected if Plugin named 'Better Messages' or 'Better Messages - for BP' is present in the plugins list
  2. Check installed version number
    In Plugins list, click on 'Better Messages' to view plugin details, or check the plugin folder file header in wp-content/plugins/better-messages/better-messages.php for 'Version:' field
    Affected if Version displayed is lower than 2.4.1 (for example, 2.4.0, 2.3.9, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the 'Better Messages' plugin shows as 'Active' (not deactivated or network deactivated)
    Affected if Plugin is active and version is below 2.4.1
  4. Verify chat/messaging functionality is in use
    Check if the site uses Better Messages for user-to-user messaging by visiting the front-end messaging page or reviewing plugin settings in WP admin under 'Better Messages' menu
    Affected if Plugin is active with messaging feature enabled and version is below 2.4.1

You are affected if Better Messages plugin is installed, active, and the installed version is any version prior to 2.4.1, since the stored XSS flaw exists in the chat message handling of vulnerable versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.1 or later
Fixed in 2.4.1
Interim mitigation

Upgrade to version 2.4.0 or later if a patched version is available; otherwise, implement proper input sanitization (sanitize_text_field, wp_kses) and output escaping (esc_html, esc_attr) on all user-generated content display points within the plugin.

Recommended fix High confidence

Better Messages version 2.4.1

  1. Backup your WordPress database and files before making any changes
  2. Navigate to WordPress Admin Dashboard > Plugins
  3. Locate 'Better Messages' in the plugins list
  4. If an update to version 2.4.1 is available, click 'Update Now'
  5. Alternatively, download version 2.4.1 from the WordPress plugin repository and upload/install it manually
  6. After updating, verify the plugin is running version 2.4.1 under Plugins > Installed Plugins
  7. Test the chat functionality to ensure the update did not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Better Messages Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49168 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data