dbcve.org
BethemeWordPress extension · Muffingroup

CVE-2025-0450

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 27.6.2 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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's custom JS functionality in all versions up to, and including, 27.6.1 due to insufficient input sanitization and output escaping on user supplied attributes. 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 an injected page.

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 plugin has a stored XSS vulnerability in its custom JS functionality. Authenticated users with contributor-level access or higher can inject malicious JavaScript through unsanitized user-supplied attributes, which executes when other users access affected pages.

MitigationUpdate Betheme to a version beyond 27.6.1 when available; otherwise, restrict contributor-level access and audit/remove any existing custom JS entries containing suspicious code.

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.6.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
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 Betheme version
    Log into WordPress admin, navigate to Betheme > Theme Options > About (or check the theme version displayed in Appearance > Themes). Alternatively, inspect /wp-content/themes/betheme/style.css and locate the 'Version:' comment in the file header.
    Affected if The installed version is lower than 27.6.2 (e.g., 27.6.1, 27.5.x, etc.)
  2. Locate custom JS settings
    In WordPress admin, go to Bethome > Theme Options > Custom JS. This section allows contributors and above to add custom JavaScript to the site.
    Affected if You have access to the Custom JS section or any custom JS code is present in the theme options database entries
  3. Inspect custom JS entries for unsanitized attributes
    Review all entries in Betheme > Theme Options > Custom JS. Look for JavaScript that uses user-supplied attributes (such as onclick, onload, onerror, or similar event handlers) without proper sanitization. Check the wp_options table for rows where option_name contains 'betheme_custom_js' or similar.
    Affected if Any custom JS entries contain unsanitized event handlers, inline scripts with user-controlled data, or suspicious-looking encoded characters that could indicate injection attempts
  4. Check for contributor-level user accounts
    Navigate to Users in WordPress admin and review roles assigned. Contributors have edit_posts capability but cannot publish. Check if any unfamiliar contributor accounts exist.
    Affected if There are active contributor-level (or higher) user accounts, especially ones not recognized or with suspicious usernames
  5. Audit recent theme option changes
    If available, check WordPress audit logs or the wp_options table for recent changes to betheme-related options, particularly around custom_js, to identify recent unauthorized modifications.
    Affected if Custom JS or theme options were modified recently by accounts that should not have had permission or that show unusual activity patterns

You are affected if Betheme version is below 27.6.2 AND the Custom JS functionality is in use or accessible to contributor-level users, particularly if untrusted contributors exist or suspicious custom JS entries are present.

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.6.2 or later
Fixed in 27.6.2
Interim mitigation

Update Betheme to a version beyond 27.6.1 when available; otherwise, restrict contributor-level access and audit/remove any existing custom JS entries containing suspicious code.

Recommended fix High confidence

Betheme version 27.6.2

  1. Backup your WordPress site before making any changes
  2. Navigate to Appearance > Themes in WordPress admin
  3. Locate Betheme in your installed themes
  4. Check if version 27.6.2 or newer is available from your theme provider
  5. Update Betheme to version 27.6.2 or the latest available version
  6. Verify the update was successful by checking the theme version
  7. Clear any caching plugins or server-side caches
  8. Test that the custom JS functionality works correctly with proper sanitization

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

Fix this in Betheme Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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