dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-1872

HIGH · 8.8 CVSS v3.1 Published 2024-03-29
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 Button plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.1.27 via deserialization of untrusted input in the button_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 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.

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 Button WordPress plugin up to version 1.1.27 is vulnerable to PHP Object Injection through unsafe deserialization of untrusted input in the button_shortcode function. Authenticated attackers with contributor-level access or higher can inject arbitrary PHP objects. While the plugin itself lacks a known POP chain, attackers can achieve RCE if another plugin or theme on the same WordPress installation provides a POP chain.

MitigationUpdate the Button plugin to version 1.1.28 or later. If unable to update immediately, audit other installed plugins and themes for potential POP chains that could be chained with this vulnerability.

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. Identify if the Button plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Button' in the list. Note: This plugin may also be named 'Button Generator' or similar.
    Affected if The Button plugin appears in the installed plugins list
  2. Determine the installed version of the Button plugin
    In the Plugins list, click on the plugin name or view details to find the version number displayed next to the plugin name.
    Affected if The version number displayed is 1.1.27 or lower (versions 1.1.28 and later contain the fix)
  3. Verify the button_shortcode functionality is accessible
    Check if the shortcode [button] or similar button shortcodes provided by the plugin are in use on any posts, pages, or widgets within the WordPress site. Shortcodes can be searched in the WordPress database via Posts > All Posts > search content for button-related shortcodes.
    Affected if Any page, post, or widget contains a button shortcode provided by this plugin and the site allows contributor-level users to create or edit content
  4. Confirm contributor-level or higher user access exists
    Review WordPress user roles at Users > All Users and check if any accounts have the 'Contributor', 'Author', 'Editor', or Administrator roles. These roles can create or edit content where the vulnerable shortcode could be inserted.
    Affected if At least one user account has Contributor level access or higher, and that user can access the WordPress admin area or use the REST API to create/edit content
  5. Check for additional plugins that may provide POP chains
    Review installed plugins and themes for known PHP Object InjectionPOP chain capabilities. Common indicators include plugins with unserialize() calls on user input, serialized data storage, or known POP chain classes.
    Affected if Other installed plugins or the active theme contain unserialize() calls that process untrusted data, which could be chained with CVE-2024-1872 to achieve RCE

A site is affected if the Button plugin versions 1.1.27 or lower are installed, the plugin is active, and at least one user with Contributor-level access exists on the site.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Button plugin to version 1.1.28 or later. If unable to update immediately, audit other installed plugins and themes for potential POP chains that could be chained with this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1872 — 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-1872 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