# CVE-2023-4023: All Users Messenger <= 1.24 - Subscriber+ Message Deletion via IDOR

> Non-administrator users can delete messages from the All Users Messenger plugin due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2023
- **Updated:** 5 May 2025
- **Also known as:** GHSA-7rm2-xq32-ww37

## What is CVE-2023-4023?

CVE-2023-4023 is a medium-severity missing authorization vulnerability in Unknown All Users Messenger, published on 30 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The All Users Messenger WordPress plugin through 1.24 does not prevent non-administrator users from deleting messages from the all-users messenger.

## Which versions are affected by CVE-2023-4023?

It affects 1 product.


Products: Riverforest-Wp All Users Messenger.

## How do I fix CVE-2023-4023?

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

## Is CVE-2023-4023 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4023 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4023 and fix it if it is affected.

What it is: CVE-2023-4023 is a medium-severity missing authorization vulnerability in Unknown All Users Messenger, published on 30 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4023 exists.

Affected product: Unknown All Users 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-2023-4023/ (Markdown: https://insights.sbomify.com/CVE-2023-4023/index.md)
```

## Sources

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

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