Security readout for executives and security teams
Plain-English summary
CVE-2026-3506 affects the WP-Chatbot for Messenger WordPress plugin through version 4.9. An unauthenticated attacker could change the site’s MobileMonkey API token and company ID, potentially redirecting visitor chatbot conversations to an attacker-controlled account. This is an integrity issue, not described as data theft or service outage.
Executive priority
Treat as a timely remediation item for affected marketing or customer-engagement sites. Business risk is visitor conversation hijacking and brand trust impact, not full site compromise based on current sources.
Technical view
The issue is CWE-862: missing authorization. Wordfence reports the plugin fails to verify whether a requester is authorized before updating MobileMonkey-related options. CVSS 3.1 is 5.3, network-accessible, low complexity, no privileges, no user interaction, with low integrity impact only.
Likely exposure
Public WordPress sites running WP-Chatbot for Messenger versions up to and including 4.9 are the relevant exposure, especially where chatbot configuration is active.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates unauthenticated network access with low attack complexity, making internet-exposed installations easier to target if reachable.
Researcher notes
Evidence supports an authorization-bypass configuration overwrite in WP-Chatbot for Messenger through 4.9. Public references include Wordfence and WordPress plugin source locations. The provided data does not name a fixed version, patch, or confirmed exploitation.
Mitigation direction
- Identify all WordPress sites using WP-Chatbot for Messenger.
- If running version 4.9 or earlier, check vendor or plugin repository guidance.
- Disable or remove the plugin where it is not business-critical.
- Review MobileMonkey API token and company ID for unauthorized changes.
- Restrict administrative change workflows and monitor chatbot destination behavior.
Validation and detection
- Inventory installed WordPress plugins and versions across managed sites.
- Confirm whether WP-Chatbot for Messenger is present and at or below 4.9.
- Inspect configured MobileMonkey account identifiers for unexpected values.
- Verify chatbot conversations route to the intended business account.
- Monitor WordPress and security logs for unexpected plugin option changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3506 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/32cce973-bc3b-45f1-ad4d-ff395d3a6c8e?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/wp-chatbot/trunk/inc/MobileMonkeyApi.php#L37CVE reference
- https://plugins.trac.wordpress.org/browser/wp-chatbot/tags/4.9/inc/MobileMonkeyApi.php#L37CVE reference
- https://plugins.trac.wordpress.org/browser/wp-chatbot/tags/4.9/admin/class-htcc-admin.php#L29CVE reference
- https://plugins.trac.wordpress.org/browser/wp-chatbot/tags/4.9/admin/admin.php#L29CVE reference
- https://plugins.trac.wordpress.org/browser/wp-chatbot/tags/4.9/inc/class-ht-cc.php#L178CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.