Live Chat With Facebook MessengerWordPress extension · Ninjateam
CVE-2023-5740
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 · uneditedThe Live Chat with Facebook Messenger plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'messenger' shortcode in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 · high confidenceThe Live Chat with Facebook Messenger WordPress plugin is vulnerable to Stored Cross-Site Scripting (XSS) in all versions up to 1.0. The 'messenger' shortcode fails to properly sanitize and escape user-supplied attributes before outputting them in HTML, allowing authenticated attackers with contributor-level or higher permissions to inject malicious JavaScript that executes when users access affected pages.
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
Live Chat With Facebook MessengerWordPress extension
<= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedGo to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Live Chat With Facebook Messenger' or 'Ninjateam Live Chat With Facebook Messenger' in the listAffected if The plugin appears in the installed plugins list
-
Identify installed plugin versionIn the Plugins list, click on the plugin name or view details to read the version number displayedAffected if Version listed is 1.0 or below
-
Locate the messenger shortcode in useSearch post/page content, widgets, or theme files for the shortcode pattern [messenger] or [messenger ...]Affected if The [messenger] shortcode is present in any published content
-
Check for untrusted contributor-level usersGo to WordPress admin > Users and review user accounts; check which users have the 'Contributor' role or higher permission levelsAffected if There are Contributor-level or higher users who are not trusted or have not been vetted
If the Ninjateam Live Chat With Facebook Messenger plugin version 1.0 or below is installed AND the [messenger] shortcode is in use, the environment is affected by this XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to a patched version once available; in the interim, restrict contributor-level permissions and review/remove shortcodes from untrusted users. The fix requires implementing proper input sanitization (e.g., esc_attr()) and output escaping (e.g., esc_html()) on all shortcode attribute parameters.
Fix this in Live Chat With Facebook Messenger
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5740 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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