# CVE-2026-9048: Missing authorization in Slider Revolution

> Authenticated contributors can extract sensitive social media API credentials from slider settings due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-qp4q-9v3r-37r2

## What is CVE-2026-9048?

CVE-2026-9048 is a medium-severity missing authorization vulnerability in Slider Revolution, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Slider Revolution plugin for WordPress is vulnerable to Sensitive Information Exposure in versions 7.0.0 - 7.0.14, via the 'slider.get.full' AJAX Action. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including raw social media API credentials: the Instagram OAuth token, Flickr API key, YouTube Data API key, and Facebook App ID, stored in any configured slider's settings.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-9048 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9048 is a medium-severity missing authorization vulnerability in Slider Revolution, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9048 in the wild and no public exploit code.

Affected product: Slider Revolution. 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-9048/ (Markdown: https://insights.sbomify.com/CVE-2026-9048/index.md)
```

## Sources

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

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