dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-6152

HIGH · 8.8 CVSS v3.1 Published 2024-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Flipbox Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.5 via deserialization of untrusted input in the flipbox_builder_Flipbox_ShortCode function. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Flipbox Builder WordPress plugin (versions up to 1.5) contains a PHP Object Injection vulnerability in the flipbox_builder_Flipbox_ShortCode function. The vulnerability stems from deserialization of untrusted input without proper validation. Authenticated attackers with Contributor-level access can inject arbitrary PHP objects. While no POP chain exists in the plugin itself, if another installed plugin or theme provides a POP chain, attackers could achieve remote code execution, file deletion, or sensitive data retrieval.

MitigationReplace unsafe unserialize() calls with json_decode() or other safe deserialization methods in the flipbox_builder_Flipbox_ShortCode function. Update to version 1.6 or later once available, or remove the plugin if no patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Flipbox Builder plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Flipbox Builder' in the installed plugins list, or check the filesystem at /wp-content/plugins/ for a folder named 'flipbox-builder' or similar
    Affected if The plugin is installed and active
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Flipbox Builder, click on the plugin name to view the version number, or inspect the main plugin file header in /wp-content/plugins/flipbox-builder/
    Affected if Version is 1.5 or earlier (the vulnerability affects versions up to 1.5)
  3. Locate the vulnerable shortcode function
    Access the site files via FTP or file manager and locate the file containing flipbox_builder_Flipbox_ShortCode function, typically in the plugin's main PHP file or includes folder
    Affected if The function exists in the installed version
  4. Check for unsafe deserialization in the shortcode function
    Open the file containing flipbox_builder_Flipbox_ShortCode and search for 'unserialize' calls within that function
    Affected if The function contains unserialize() calls processing untrusted input
  5. Determine if shortcode is in active use
    Search WordPress posts, pages, or widget areas for the flipbox_builder shortcode (commonly [flipbox] or similar), or check the plugin's flipbox post type if it uses custom post types
    Affected if The shortcode is actively used on the site, allowing contributor-level users to trigger the vulnerable code path

The environment is affected if Flipbox Builder plugin version 1.5 or earlier is installed and the flipbox_builder_Flipbox_ShortCode function contains unserialize() calls processing user-supplied data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace unsafe unserialize() calls with json_decode() or other safe deserialization methods in the flipbox_builder_Flipbox_ShortCode function. Update to version 1.6 or later once available, or remove the plugin if no patch is released.

Recommended fix Moderate confidence

Version 1.5.1 or latest available version of Flipbox Builder plugin for WordPress

  1. Check the current version of the Flipbox Builder plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Flipbox Builder and note the current version
  4. Upgrade the Flipbox Builder plugin to the latest available version (1.5.1 or higher)
  5. Verify the upgrade was successful and the new version is active
  6. Ensure users with Contributor-level or higher access are trusted, as this vulnerability requires authentication to exploit

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6152 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data