CVE-2024-1792: CWE-502 Deserialization of Untrusted Data in jtsternberg CMB2
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.
AI Analysis
Technical Summary
The CMB2 plugin for WordPress suffers from a deserialization vulnerability (CWE-502) in the text_datetime_timestamp_timezone field, enabling PHP Object Injection. This affects all versions up to and including 2.10.1. Exploitation requires authenticated contributor-level access or higher and a metabox activation in the site’s codebase. The plugin does not contain a POP chain internally, so exploitation depends on the presence of additional vulnerable plugins or themes that provide such a chain, which could escalate the impact to arbitrary file deletion, data theft, or remote code execution.
Potential Impact
Successful exploitation can lead to high-impact consequences including arbitrary file deletion, sensitive data exposure, and remote code execution, but only if a POP chain is present in other installed components. The vulnerability requires authenticated access with contributor or higher privileges and specific site configuration (metabox activation). Without these conditions, exploitation is not feasible.
Mitigation Recommendations
No official patch or fix is currently available for this vulnerability. Users should review their WordPress installations for the presence of the CMB2 plugin version 2.10.1 or earlier and consider removing or disabling it if not needed. Additionally, verify whether metabox activation is used in the site’s code (e.g., functions.php) and assess installed plugins and themes for potential POP chains that could be leveraged. Monitor vendor advisories for updates or patches addressing this issue.
CVE-2024-1792: CWE-502 Deserialization of Untrusted Data in jtsternberg CMB2
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The CMB2 plugin for WordPress suffers from a deserialization vulnerability (CWE-502) in the text_datetime_timestamp_timezone field, enabling PHP Object Injection. This affects all versions up to and including 2.10.1. Exploitation requires authenticated contributor-level access or higher and a metabox activation in the site’s codebase. The plugin does not contain a POP chain internally, so exploitation depends on the presence of additional vulnerable plugins or themes that provide such a chain, which could escalate the impact to arbitrary file deletion, data theft, or remote code execution.
Potential Impact
Successful exploitation can lead to high-impact consequences including arbitrary file deletion, sensitive data exposure, and remote code execution, but only if a POP chain is present in other installed components. The vulnerability requires authenticated access with contributor or higher privileges and specific site configuration (metabox activation). Without these conditions, exploitation is not feasible.
Mitigation Recommendations
No official patch or fix is currently available for this vulnerability. Users should review their WordPress installations for the presence of the CMB2 plugin version 2.10.1 or earlier and consider removing or disabling it if not needed. Additionally, verify whether metabox activation is used in the site’s code (e.g., functions.php) and assess installed plugins and themes for potential POP chains that could be leveraged. Monitor vendor advisories for updates or patches addressing this issue.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2024-02-22T19:44:58.422Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6d3eb7ef31ef0b56f542
Added to database: 2/25/2026, 9:44:30 PM
Last enriched: 4/9/2026, 7:08:07 AM
Last updated: 4/12/2026, 12:43:15 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.