CVE-2026-1924

Aruba HiSpeed Cache <= 3.0.4 - Cross-Site Request Forgery to Plugin Settings Reset

2026-04-09 12:50
Legion Hunter

Strategic Overview

Status
Patched in 3.0.5
Affected Plugin
Aruba HiSpeed Cache
Affected Version
<= 3.0.4
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-1924
View all Aruba HiSpeed Cache vulnerabilities

At a glance

CVE-2026-1924 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Aruba HiSpeed Cache WordPress plugin, affecting versions <= 3.0.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.5; sites on affected versions should update now. Disclosed April 2026, reported by Legion Hunter.

Vulnerability Overview

The Aruba HiSpeed Cache plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0.4. This is due to missing nonce verification on the `ahsc_ajax_reset_options()` function. This makes it possible for unauthenticated attackers to reset all plugin settings to their default values via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE-2026-23694 is a duplicate of this.

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.

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

Aruba HiSpeed Cache <= 3.0.4 carries this weakness at ahsc_ajax_reset_options(), and reaching it 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 Aruba HiSpeed Cache the fix is 3.0.5: builds <= 3.0.4 are affected, anything from 3.0.5 onward is not.

Remediation

Update to version 3.0.5, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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