Betheme <= 26.6.2 - Authenticated (Subscriber+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 26.6.3
- Affected Theme
- Betheme
- Affected Version
<= 26.6.2- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-45363
At a glance
CVE-2022-45363 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Betheme WordPress theme, affecting versions <= 26.6.2. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 26.6.3; sites on affected versions should update now. Disclosed November 2022, reported by Dave Jong.
Vulnerability Overview
The Betheme theme for WordPress is vulnerable to authorization bypass that leads to stored Cross-Site Scripting in versions up to, and including, 26.6.2. This is due to a missing capability check on the mfnvb_init_vb() function that initializes the visual editor for the plugin and discloses the plugin's page builder nonces and functionality to an attacker. This makes it possible for authenticated attacks with minimal permissions, such as a subscriber, to trigger the Betheme page editor for any post or page and view the information along with make any changes to the post/page accessed through the editor. This CVE is specific to being able to inject malicious JavaScript into the pages and posts that can be edited by the plugin as a result of the initial missing authorization vulnerability. This is an extension of CVE-2022-45356.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Betheme <= 26.6.2 carries this weakness at mfnvb_init_vb(), and reaching it takes an account at Subscriber level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Betheme the fix is 26.6.3: builds <= 26.6.2 are affected, anything from 26.6.3 onward is not.
Remediation
Update to version 26.6.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Betheme 26.6.3 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2026-6178: Betheme <= 28.4 Stored Cross-Site Scripting
CVE-2026-6178 - 6.4CVE-2025-9371: Betheme <= 28.1.6 Stored Cross-Site Scripting
CVE-2025-9371 - 6.4CVE-2025-63075: Betheme <= 28.2 Stored Cross-Site Scripting
CVE-2025-63075 - 6.4CVE-2025-7399: Betheme <= 28.1.3 Stored Cross-Site Scripting
CVE-2025-7399
Other vulnerabilities in Betheme
- 8.8CVE-2026-65548: Betheme <= 28.5.7 Remote Code Execution
CVE-2026-65548 - 8.8CVE-2026-6261: Betheme <= 28.4 Arbitrary File Upload to RCE
CVE-2026-6261 - 8.8CVE-2024-2694: Betheme <= 27.5.6 PHP Object Injection
CVE-2024-2694 - 8.8CVE-2022-45356: Betheme Missing Authorization Check on Core
CVE-2022-45356 - 8.8CVE-2022-3861: Betheme <= 26.5.1.4 PHP Object Injection
CVE-2022-3861 - 8.8CVE-2022-45077: Betheme <= 26.5.1.4 PHP Object Injection
CVE-2022-45077 - 6.5CVE-2026-6262: Betheme <= 28.4 Arbitrary File Deletion
CVE-2026-6262 - 6.5CVE-2023-39998: Betheme <= 27.1.1 Missing Authorization
CVE-2023-39998
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C