# CVE-2023-0453: WP Private Message < 1.0.6 - Private Message Disclosure via IDOR

> Authenticated users can read other users' private messages by tampering with message IDs in the WP Private Message plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 21 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-849q-f682-346f

## What is CVE-2023-0453?

CVE-2023-0453 is a medium-severity missing authorization vulnerability in Unknown WP Private Message, published on 21 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Private Message WordPress plugin (bundled with the Superio theme as a required plugin) before 1.0.6 does not ensure that private messages to be accessed belong to the user making the requests. This allowing any authenticated users to access private messages belonging to other users by tampering the ID.

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

It affects 1 product.


Products: Apusthemes Wp Private Messaging.

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

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

## Is CVE-2023-0453 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0453 is a medium-severity missing authorization vulnerability in Unknown WP Private Message, published on 21 Feb 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-0453 exists.

Affected product: Unknown WP Private Message. 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-0453/ (Markdown: https://insights.sbomify.com/CVE-2023-0453/index.md)
```

## Sources

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

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