dbcve.org
BethemeWordPress extension · Muffingroup

CVE-2024-2694

HIGH · 8.8 CVSS v3.1 Published 2024-08-30
Fix available
A fix is available. Upgrade to after 27.5.6 or later.
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 Betheme theme for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 27.5.6 via deserialization of untrusted input of the 'mfn-page-items' post meta value. 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 Betheme WordPress theme up to version 27.5.6 is vulnerable to PHP Object Injection. The theme deserializes untrusted data from the 'mfn-page-items' post meta value without proper sanitization, allowing authenticated attackers with contributor-level access or higher to inject arbitrary PHP objects. While no POP chain exists within the theme itself, additional plugins or themes installed on the target could provide one, enabling remote code execution, file deletion, or data exfiltration.

MitigationUpdate Betheme theme to version 27.5.7 or later to remediate this vulnerability. If immediate updating is not feasible, audit and restrict contributor-level user permissions and review installed plugins/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.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BethemeWordPress extension
Affected:<= 27.5.6

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. Confirm Betheme theme is installed
    Locate the Betheme theme folder in the WordPress themes directory (/wp-content/themes/betheme/) or verify its presence in the WordPress admin under Appearance > Themes
    Affected if Betheme theme is present in the WordPress installation
  2. Determine the installed Betheme version
    Read the version number from the theme's style.css file header located in the betheme theme folder, or check the theme details displayed in the WordPress admin theme list
    Affected if Unable to determine the version or the theme is not properly installed
  3. Compare version against affected range
    Compare the installed version number to the vulnerable range: version 27.5.6 and below
    Affected if Installed version is 27.5.6 or lower (any version <=27.5.6 indicates the vulnerable version is in use)

A user is affected if Betheme theme version 27.5.6 or lower is installed and active on their WordPress 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.

dbcve · scoped
Upgrade available Upgrade to a release after 27.5.6
Interim mitigation

Update Betheme theme to version 27.5.7 or later to remediate this vulnerability. If immediate updating is not feasible, audit and restrict contributor-level user permissions and review installed plugins/themes for potential POP chains that could be chained with this vulnerability.

Recommended fix Moderate confidence

Betheme version 27.5.7 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Download the latest version of Betheme (version 27.5.7 or higher) from your ThemeForest account
  3. 3. Navigate to Appearance > Themes in your WordPress admin dashboard
  4. 4. Deactivate the current Betheme theme or replace it with another active theme temporarily
  5. 5. Delete the existing Betheme theme (or ensure you have a backup)
  6. 6. Install the updated Betheme 27.5.7+ theme via WordPress or upload the new theme zip file
  7. 7. Reactivate Betheme and verify the site functions correctly
  8. 8. Test that users with contributor-level access can no longer exploit the deserialization vulnerability through the mfn-page-items post meta
Caveat Minor: Review custom styling and child theme configurations after theme update to ensure compatibility; always test on staging first

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

Fix this in Betheme Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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