# CVE-2024-1204: Meta Box < 5.9.4 - Contributor+ Arbitrary Posts' Custom Field Disclosure

> Contributors can access arbitrary custom fields from other users' posts due to missing authorization checks in the Meta Box 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:** 15 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6mpg-x75c-hw5v

## What is CVE-2024-1204?

CVE-2024-1204 is a medium-severity missing authorization vulnerability in Unknown Meta Box , published on 15 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Meta Box  WordPress plugin before 5.9.4 does not prevent users with at least the contributor role from access arbitrary custom fields assigned to other user's posts.

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

It affects 1 product.


Products: Metabox Meta Box.

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

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

## Is CVE-2024-1204 being exploited?

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

## Other vulnerabilities in Unknown Meta Box 

- [CVE-2019-14794](https://insights.sbomify.com/CVE-2019-14794/): File upload in n/a (high 7.5)
- [CVE-2019-14793](https://insights.sbomify.com/CVE-2019-14793/): Missing authorization in n/a (medium 6.5)
- [CVE-2023-6526](https://insights.sbomify.com/CVE-2023-6526/): Meta Box – WordPress Custom Fields Framework <= 5.9.2 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1204 is a medium-severity missing authorization vulnerability in Unknown Meta Box , published on 15 Apr 2024. 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-2024-1204 exists.

Affected product: Unknown Meta Box . 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-1204/ (Markdown: https://insights.sbomify.com/CVE-2024-1204/index.md)
```

## Sources

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

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