dbcve.org
BethemeWordPress extension · Muffingroup

CVE-2023-47770

HIGH · 7.6 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 27.1.2 or later.
See remediation →
82/100
Remediation priority · High
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
Missing Authorization vulnerability in Muffin Group Betheme.This issue affects Betheme: from n/a through 27.1.1.

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 · moderate confidence

Missing Authorization vulnerability in Muffin Group Betheme WordPress theme allows attackers to access functionality they shouldn't have permission to access. The specific attack vector and affected functionality are not detailed in available sources, but authorization bypasses in WordPress themes typically allow unauthorized users to access admin-level or privileged operations.

MitigationUpdate Betheme to the latest version (27.1.1 or later) which contains the fix for this authorization issue. If immediate update is not possible, restrict access to the theme's admin functions via server-level access controls.

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.1.2

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
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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
    In WordPress admin, go to Appearance > Themes and verify the Betheme theme is installed and/or active. Alternatively, check the theme directory at /wp-content/themes/betheme/ for the existence of style.css which contains theme metadata.
    Affected if Betheme theme is present in the WordPress installation regardless of active status
  2. Identify installed Betheme version
    Open the file /wp-content/themes/betheme/style.css in a text editor or via command line (e.g., cat style.css | grep -i 'Version'). The version number is listed in the theme header comments.
    Affected if The version listed is less than 27.1.2 (e.g., 27.1.1, 27.0.x, 26.x, etc.)
  3. Audit theme AJAX and callback endpoints
    Search theme files for registered WordPress hooks involving admin capabilities: grep -r 'add_action' or 'add_filter' within /wp-content/themes/betheme/ looking for AJAX actions (wp_ajax_), admin_init, or any hooks referencing 'manage_options', 'edit_users', or similar privileged capabilities.
    Affected if Theme registers any AJAX endpoints or admin hooks without proper capability checks (current_user_can() missing or using low-privilege checks)
  4. Review theme file permissions and direct access
    Check PHP files in /wp-content/themes/betheme/ for direct access guards (typically: if (!defined('ABSPATH')) exit;) at the top. Also examine any files in includes/ or functions/ directories that may be accessible via direct URL.
    Affected if Theme files lack ABSPATH guards or contain accessible files that perform sensitive operations without authorization verification

A user is affected if Betheme theme version is below 27.1.2 AND the site exposes theme-based AJAX endpoints or admin functions accessible to unauthorized users.

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

Update Betheme to the latest version (27.1.1 or later) which contains the fix for this authorization issue. If immediate update is not possible, restrict access to the theme's admin functions via server-level access controls.

Recommended fix Moderate confidence

Betheme 27.1.2

  1. 1. Backup your WordPress site before making any changes
  2. 2. Download Betheme version 27.1.2 from your theme provider or theme forest/author
  3. 3. Navigate to Appearance > Themes in WordPress admin dashboard
  4. 4. Upload and activate Betheme version 27.1.2
  5. 5. Verify the theme version shows 27.1.2 in Appearance > Themes
  6. 6. Test critical site functionality to ensure the upgrade works correctly

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

Fix this in Betheme 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 the upgrade done

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-2023-47770 — 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-2023-47770 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