CVE-2025-26748

Arkhe <= 3.11.0 - Cross-Site Request Forgery to Local File Inclusion

2025-04-11 00:00
Dimas Maulana

Strategic Overview

Status
Patched in 3.12.0
Affected Theme
Arkhe
Affected Version
<= 3.11.0
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-26748
View all Arkhe vulnerabilities

At a glance

CVE-2025-26748 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Arkhe WordPress theme, affecting versions <= 3.11.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.12.0; sites on affected versions should update now. Disclosed April 2025, reported by Dimas Maulana.

Vulnerability Overview

The Arkhe theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.11.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to include and execute code in files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Arkhe <= 3.11.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Arkhe the fix is 3.12.0: builds <= 3.11.0 are affected, anything from 3.12.0 onward is not.

Remediation

Update to version 3.12.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Arkhe: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Arkhe 3.12.0 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Alerts

External References

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