# CVE-2026-86786: Slider Pro <= 1.0.0 - Unauthenticated Sensitive Data Disclosure via sliderpro_multiple_images

> Unauthenticated attackers can access sensitive data from non-public posts and media metadata due to missing authorization checks in the Slider Pro plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-3qh5-h6hm-64fg

## What is CVE-2026-86786?

CVE-2026-86786 is a medium-severity missing authorization vulnerability in Unknown Slider Pro, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Slider Pro WordPress plugin through 1.0.0 does not perform any capability or authorisation check on one of its AJAX actions, allowing unauthenticated users to retrieve the title, excerpt and permalink of non-public posts, including drafts, pending, scheduled, private and trashed posts, as well as post revisions and media metadata.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-86786?


## How do I fix CVE-2026-86786?

No fix has been published for CVE-2026-86786 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86786 being exploited?

There is no known exploitation of CVE-2026-86786 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86786 and fix it if it is affected.

What it is: CVE-2026-86786 is a medium-severity missing authorization vulnerability in Unknown Slider Pro, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86786 in the wild and no public exploit code.

Affected product: Unknown Slider Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86786/ (Markdown: https://insights.sbomify.com/CVE-2026-86786/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86786
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86786
- OSV: https://osv.dev/vulnerability/CVE-2026-86786

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86786/
Summaries are generated and may contain mistakes; the official description above is the record.
