CVE-2026-3058

Seraphinite Accelerator <= 2.28.14 - Authenticated (Subscriber+) Exposure of Sensitive Information to an Unauthorized Actor

2026-03-03 22:00
lucsob

Strategic Overview

Status
Patched in 2.28.15
Affected Version
<= 2.28.14
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-3058
View all Seraphinite Accelerator vulnerabilities

At a glance

CVE-2026-3058 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Seraphinite Accelerator WordPress plugin, affecting versions <= 2.28.14. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.28.15; sites on affected versions should update now. Disclosed March 2026, reported by lucsob.

Vulnerability Overview

The Seraphinite Accelerator plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.28.14 via the `seraph_accel_api` AJAX action with `fn=GetData`. This is due to the `OnAdminApi_GetData()` function not performing any capability checks. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive operational data including cache status, scheduled task information, and external database state.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Seraphinite Accelerator <= 2.28.14 carries this weakness at OnAdminApi_GetData(), and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Seraphinite Accelerator the fix is 2.28.15: builds <= 2.28.14 are affected, anything from 2.28.15 onward is not.

Remediation

Update to version 2.28.15, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Seraphinite Accelerator 2.28.15 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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