# CVE-2024-49639: WordPress Monitor.chat plugin <= 1.1.1 - Reflected Cross Site Scripting (XSS) vulnerability

> Reflected XSS in Monitor.chat plugin allows attackers to execute arbitrary scripts in victim browsers via crafted URLs.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Oct 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-mw8q-c9cq-qfgc

## What is CVE-2024-49639?

CVE-2024-49639 is a high-severity cross-site scripting vulnerability in Edward Stoever Monitor.chat, published on 29 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Edward Stoever Monitor.chat monitor-chat allows Reflected XSS.This issue affects Monitor.chat: from n/a through <= 1.1.1.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-49639?

It affects 1 product.


Products: Edwardstoever Monitor.chat.

## How do I fix CVE-2024-49639?

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

## Is CVE-2024-49639 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49639 and fix it if it is affected.

What it is: CVE-2024-49639 is a high-severity cross-site scripting vulnerability in Edward Stoever Monitor.chat, published on 29 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-49639 in the wild and no public exploit code.

Affected product: Edward Stoever Monitor.chat. 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-2024-49639/ (Markdown: https://insights.sbomify.com/CVE-2024-49639/index.md)
```

## Sources

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

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