dbcve.org
BethemeWordPress extension · Muffingroup

CVE-2022-45077

HIGH · 8.8 CVSS v3.1 Published 2022-11-17
Fix available
A fix is available. Upgrade to 26.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
Auth. (subscriber+) PHP Object Injection vulnerability in Betheme theme <= 26.5.1.4 on WordPress.

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

Authenticated PHP Object Injection vulnerability in Betheme theme for WordPress allows subscribers and higher privileged users to potentially achieve remote code execution through deserialization of untrusted input.

MitigationUpdate Betheme theme to version greater than 26.5.1.4. If unable to update immediately, disable the theme or restrict user registrations until the patch can be applied.

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:< 26.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. Identify Betheme theme installation
    Check your WordPress installation for the Betheme theme by examining the theme directory (wp-content/themes/betheme) and locate the style.css file which contains the theme version in the header comment
    Affected if The theme is installed and the version field shows a version lower than 26.6
  2. Compare installed version to affected range
    Read the Version: X.X line from the Betheme theme style.css header and compare it numerically against 26.6
    Affected if The installed version is less than 26.6 (for example, 26.5, 26.4, etc.)
  3. Determine if user registration is enabled
    In WordPress admin dashboard, go to Settings > General and check the 'Membership' setting 'Anyone can register' - or query the wp_options table for the 'users_can_register' option value
    Affected if User registration is enabled, allowing low-privileged subscriber accounts to be created
  4. Verify authenticated access exists
    Review existing user accounts in Users > All Users or query wp_users table to identify accounts with Subscriber, Contributor, Author, Editor, or Administrator roles
    Affected if Any user accounts exist with subscriber-level or higher privileges, providing the authentication needed for this exploit

You are affected if Betheme theme version is below 26.6 AND authenticated user accounts (subscriber or higher) can exist in your WordPress installation.

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 26.6 or later
Fixed in 26.6
Interim mitigation

Update Betheme theme to version greater than 26.5.1.4. If unable to update immediately, disable the theme or restrict user registrations until the patch can be applied.

Recommended fix High confidence

Betheme version 26.6 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Betheme theme in the themes list
  4. 4. Click on Betheme theme to view details
  5. 5. If an update is available, click the "Update Now" button to update to version 26.6 or later
  6. 6. Alternatively, download the latest version of Betheme (26.6 or higher) from themeforest.net and upload it via Appearance > Themes > Add New > Upload Theme
  7. 7. After updating, clear any caching plugins and verify the site functionality
Caveat Theme updates may include template or style changes; review theme changelog and test on staging site before production deployment

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

Fix this in Betheme Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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