CVE-2026-7636

Slider by Soliloquy <= 2.8.1 - Authenticated (Subscriber+) Information Disclosure via REST API Endpoint

2026-05-21 19:23
Kitch

Strategic Overview

Status
Patched in 2.8.2
Affected Version
<= 2.8.1
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-7636
View all Slider by Soliloquy – Responsive Image Slider for WordPress vulnerabilities

At a glance

CVE-2026-7636 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Slider by Soliloquy WordPress plugin, affecting versions <= 2.8.1. 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.8.2; sites on affected versions should update now. Disclosed May 2026, reported by Kitch.

Vulnerability Overview

The Slider by Soliloquy – Responsive Image Slider for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.8.1 via the map_meta_cap. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract draft slider metadata including unpublished media URLs, captions, and slider configuration authored by administrators or editors.

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

Reaching this weakness in Slider by Soliloquy <= 2.8.1 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 Slider by Soliloquy the fix is 2.8.2: builds <= 2.8.1 are affected, anything from 2.8.2 onward is not.

Remediation

Update to version 2.8.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Slider by Soliloquy 2.8.2 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