# CVE-2024-13697: Server-side request forgery in Better Messages – Live Chat, Chat Rooms, Real-Time Messaging & Private Messages

> Unauthenticated attackers can exploit a Server-Side Request Forgery vulnerability in the Better Messages WordPress plugin to access internal services.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** 1 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9pph-j6v9-q8xv

## What is CVE-2024-13697?

CVE-2024-13697 is a medium-severity server-side request forgery vulnerability in wordplus Better Messages – Live Chat, Chat Rooms, Real-Time Messaging & Private Messages, published on 1 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Better Messages – Live Chat for WordPress, BuddyPress, PeepSo, Ultimate Member, BuddyBoss plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.7.4 via the 'nice_links'. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. Successful exploitation requires the "Enable link previews" to be enabled (default).

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Wordplus Better Messages.

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

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

## Is CVE-2024-13697 being exploited?

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

## Other vulnerabilities in wordplus Better Messages – Live Chat, Chat Rooms, Real-Time Messaging & Private Messages

- [CVE-2021-24809](https://insights.sbomify.com/CVE-2021-24809/): BP Better Messages < 1.9.9.41 - Multiple CSRF (high 8.8)
- [CVE-2022-33142](https://insights.sbomify.com/CVE-2022-33142/): WordPress Better Messages plugin <= 1.9.10.57 - Denial Of Service (DoS) vulnerability (high 7.7)
- [CVE-2024-13611](https://insights.sbomify.com/CVE-2024-13611/): Information disclosure in Better Messages – Live Chat, Chat Rooms, Real-Time Messaging & Private Messages (high 7.5)
- [CVE-2023-49168](https://insights.sbomify.com/CVE-2023-49168/): WordPress BP Better Messages Plugin <= 2.4.0 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2024-13612](https://insights.sbomify.com/CVE-2024-13612/): Cross-site scripting in Better Messages – Live Chat, Chat Rooms, Real-Time Messaging & Private Messages (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13697 is a medium-severity server-side request forgery vulnerability in wordplus Better Messages – Live Chat, Chat Rooms, Real-Time Messaging & Private Messages, published on 1 Mar 2025. 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-2024-13697 in the wild and no public exploit code.

Affected product: wordplus Better Messages – Live Chat, Chat Rooms, Real-Time Messaging & Private Messages. 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-13697/ (Markdown: https://insights.sbomify.com/CVE-2024-13697/index.md)
```

## Sources

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

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