dbcve.org
BethemeWordPress extension · Muffingroup

CVE-2024-5567

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-13
Fix available
A fix is available. Upgrade to 27.5.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 27.5.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

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.5 allows authenticated users with Contributor-level access or higher to upload SVG files containing malicious JavaScript. Since SVG files are rendered as documents in browsers, the embedded scripts execute when users access the uploaded files, creating a stored XSS payload that persists on the server.

MitigationUpdate Betheme theme to version 27.6.0 or later. For sites unable to update immediately, disable SVG uploads via plugin or server configuration, and audit existing uploads for malicious content.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installed Betheme theme version
    In WordPress admin, go to Appearance > Themes and locate Betheme. The version number is displayed on the theme card or click theme details to view version info. Alternatively, check the style.css file in wp-content/themes/betheme/ for the Version: header.
    Affected if Version is less than 27.5.5 (the theme is vulnerable)
  2. Confirm SVG upload capability is accessible
    Verify that authenticated users with Contributor role or higher can access the media upload functionality. In WordPress, check if users with Contributor role can upload files by attempting to add media to a post or checking user role capabilities under Users > All Users.
    Affected if Contributor-level or higher users have access to media uploads (vulnerability is exploitable)
  3. Check for SVG files in media library
    Go to Media > Library in WordPress admin. Filter or search for .svg files. Check the file count and recent uploads. Note: SVG support may require a plugin in older WordPress versions.
    Affected if SVG files exist in the uploads directory (potential malicious payload storage)
  4. Inspect recent SVG files for suspicious content
    Download or view the content of uploaded SVG files. Look for <script> tags, javascript: URLs, onload/onerror/onclick event handlers, or foreignObject elements that may contain malicious scripts.
    Affected if SVG files contain embedded JavaScript code or event handlers (active XSS payload present)

You are affected if Betheme version is below 27.5.5 AND Contributor-level users have access to media uploads, as the combination enables the stored XSS vulnerability via SVG file uploads.

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.5.5 or later
Fixed in 27.5.5
Interim mitigation

Update Betheme theme to version 27.6.0 or later. For sites unable to update immediately, disable SVG uploads via plugin or server configuration, and audit existing uploads for malicious content.

Recommended fix High confidence

Betheme version 27.5.5 or latest stable release

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Betheme theme
  4. 4. Check the current version number displayed on the theme card
  5. 5. If the installed version is below 27.5.5, click on the theme to access details and select Update Available if shown, or download the latest version from the theme vendor
  6. 6. Alternatively, download the updated theme package from support.muffingroup.com or themeforest.net
  7. 7. Update the theme to version 27.5.5 or the latest available version
  8. 8. After updating, verify the fix by testing SVG file upload functionality to ensure malicious scripts are properly sanitized
Caveat Ensure custom child theme modifications and any customizations to theme core files are compatible with the new version before deploying to production

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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