# CVE-2024-1792: CMB2 <= 2.10.1 - Authenticated (Contributor+) PHP Object Injection

> Authenticated contributors can exploit PHP object injection in CMB2 to potentially execute code or access data if a POP chain exists.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 9 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fq8c-827p-q5gh

## What is CVE-2024-1792?

CVE-2024-1792 is a high-severity unsafe deserialization vulnerability in jtsternberg CMB2, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The CMB2 plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.10.1 via deserialization of untrusted input from the text_datetime_timestamp_timezone field. This makes it possible for authenticated attackers, with contributor access or higher, to inject a PHP Object. No POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. Please note that the plugin is a developer toolkit. For the vulnerability to become exploitable, the presence of a metabox activation in your code (via functions.php for example) is required.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2024-1792 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1792 is a high-severity unsafe deserialization vulnerability in jtsternberg CMB2, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1792 in the wild and no public exploit code.

Affected product: jtsternberg CMB2. 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-1792/ (Markdown: https://insights.sbomify.com/CVE-2024-1792/index.md)
```

## Sources

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

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