CVE-2026-65548

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

2026-07-28 00:00
daroo

Strategic Overview

Status
Patched in 28.5.8
Affected Theme
Betheme
Affected Version
<= 28.5.7
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.5.7. 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. The issue is fixed in version 28.5.8; sites on affected versions should update now. 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.5.7. 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.5.7 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. For Betheme the fix is 28.5.8: builds <= 28.5.7 are affected, anything from 28.5.8 onward is not.

Remediation

Update to version 28.5.8, or a newer patched version

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. None of that substitutes for the fix: Betheme 28.5.8 closes this, and updating the theme is the step that ends it.

  • 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