# CVE-2026-3506: WP-Chatbot for Messenger <= 4.9 - Missing Authorization to Unauthenticated Chatbot Configuration Takeover

> Unauthenticated attackers can overwrite chatbot configuration options to hijack visitor conversations, affecting WordPress sites using this plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-28gh-r3vv-g85j

## What is CVE-2026-3506?

CVE-2026-3506 is a medium-severity missing authorization vulnerability in larrykim WP-Chatbot for Messenger, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP-Chatbot for Messenger plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the site's MobileMonkey API token and company ID options, which can be used to hijack chatbot configuration and redirect visitor conversations to an attacker-controlled MobileMonkey account.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-3506?


## How do I fix CVE-2026-3506?

No fix has been published for CVE-2026-3506 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3506 being exploited?

There is no known exploitation of CVE-2026-3506 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3506 and fix it if it is affected.

What it is: CVE-2026-3506 is a medium-severity missing authorization vulnerability in larrykim WP-Chatbot for Messenger, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3506 in the wild and no public exploit code.

Affected product: larrykim WP-Chatbot for Messenger. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3506/ (Markdown: https://insights.sbomify.com/CVE-2026-3506/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3506
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3506
- OSV: https://osv.dev/vulnerability/CVE-2026-3506

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3506/
Summaries are generated and may contain mistakes; the official description above is the record.