BethemeWordPress extension · Muffingroup
CVE-2022-45363
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 · uneditedAuth. (subscriber+) Stored Cross-Site Scripting (XSS) in Muffingroup Betheme theme <= 26.6.1 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 confidenceStored XSS vulnerability in the Muffingroup Betheme WordPress theme allows authenticated users with subscriber-level privileges or higher to inject malicious JavaScript code through theme parameters, which is then executed when other users view the affected 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
<= 26.6.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Betheme theme versionIn WordPress admin, go to Appearance > Themes and locate the Betheme theme. The version number is displayed on the theme card or in the theme details panel.Affected if Version displayed is 26.6.1 or lower
-
Verify theme is activeConfirm that Betheme is the currently active theme in Appearance > Themes.Affected if Betheme is active and version is 26.6.1 or lower
-
Check for subscriber-level user accountsNavigate to Users in WordPress admin and review the role column. Look for any accounts assigned the Subscriber role.Affected if Subscriber accounts exist in the system
-
Inspect theme parameter settings for script injectionsReview theme options (typically under Betheme > Theme Options) and any custom code or header/footer injection fields for suspicious script tags, event handlers, or encoded content.Affected if Theme parameters contain unrecognized JavaScript code or script tags
You are affected if Betheme theme version 26.6.1 or lower is active AND subscriber-level user accounts can be created or already exist in your WordPress installation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the Betheme theme to a version newer than 26.6.1. If immediate update is not possible, restrict subscriber-level account creation or implement a WAF to mitigate XSS attacks.
Betheme > 26.6.1 (latest available version)
- Check current Betheme version in WordPress dashboard under Appearance > Themes
- Backup the WordPress site before making changes
- Navigate to Appearance > Themes and update Betheme to the latest available version
- Verify the update completed successfully
- Test the updated theme to ensure functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Betheme
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45363 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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