CVE-2022-45356 is a medium severity (CVSS 5.4) missing authorization flaw in the Muffin Group Betheme WordPress theme, versions up to and including 26.6.1. A low privilege account can reach it. No fixed version could be confirmed, so update to the newest release.
What's affected
The record lists Betheme from Muffingroup, from the first release through 26.6.1. I could not retrieve a fixed version. The Patchstack page blocked automated access, so check the plugin changelog or the Patchstack entry for the first patched release.
The record scores it 5.4 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L. The weakness class is CWE-862 (Missing Authorization).
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every theme with its version and whether an update is waiting:
wp theme list --fields=name,status,version,update
Look for the folder betheme. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Appearance, Themes screen in the dashboard and read the version shown under the name. Version 26.6.1 or lower is affected, and I could not confirm the first fixed version.
Check staging copies, old multisite subsites and inactive themes too. A deactivated theme is still on disk, and some of these bugs are reachable through files that load even when the theme is switched off, so deactivation alone is not a fix. Delete what you do not use.
What to do now
- Check the theme changelog for the release that fixes this CVE and update to it, or to the newest release.
- Confirm who is responsible for updating the theme, since commercial themes often update outside the normal plugin flow.
- Review the site's user list and remove accounts you do not recognise.
- Turn on automatic updates for the theme so the next fix lands without a ticket.
Why it matters
Betheme is a commercial theme bundle sold through ThemeForest, and it is installed on a large number of sites. The record describes a missing authorization flaw affecting versions through 26.6.1. The vector requires a low privilege account and scores low integrity and availability impact.
The Patchstack page for this entry blocked automated access, so I cannot give you the fixed version or the exact action involved. What I can say is that commercial themes update through the vendor's own channel, not always through the WordPress dashboard, and sites bought from resellers or through agencies often fall behind. That update path is the real risk here.
Check how your Betheme copy gets updates and whether anyone owns that job. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Quick check
How do commercial themes get updated?
Often through the vendor's license and the theme's own update screen, or through the marketplace where it was bought, not through the wordpress.org directory. Confirm which route applies to your site.
Is there a fixed version?
I could not confirm one because the Patchstack page blocked access. Check the theme changelog.
Sources
Reference from the NVD record, not retrievable when this was reviewed: Patchstack entry for Betheme 26.6.1.
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.