CVE-2026-65548

Betheme <= 28.4.2 - Authenticated (Contributor+) Remote Code Execution

2026-07-28 00:00
daroo

Strategic Overview

Status
Unpatched
Affected Theme
Betheme
Affected Version
<= 28.4.2
CVSS
8.8High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-65548
View all Betheme vulnerabilities

At a glance

CVE-2026-65548 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Betheme WordPress theme, affecting versions <= 28.4.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2026, reported by daroo.

Vulnerability Overview

The Betheme theme for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 28.4.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Betheme <= 28.4.2 takes an account at Contributor level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. No fixed build of this theme is recorded for Betheme yet, so installs running <= 28.4.2 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

An attacker needs Contributor 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-65548https://www.wordfence.com/threat-intel/vulnerabilities/id/390a541e-68dd-43dd-8fe4-5334c534552chttps://nvd.nist.gov/vuln/detail/CVE-2026-65548

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C