# CVE-2015-3634: Information disclosure in n/a

> Remote attackers can read arbitrary WordPress option values via the Slideshow plugin's AJAX stylesheet loading function.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 8 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-prcg-m67x-cqrh

## What is CVE-2015-3634?

CVE-2015-3634 is a high-severity vulnerability in n/a, published on 8 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SlideshowPluginSlideshowStylesheet::loadStylesheetByAJAX function in the Slideshow plugin 2.2.8 through 2.2.21 for Wordpress allows remote attackers to read arbitrary Wordpress option values.

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

## Which versions are affected by CVE-2015-3634?

It affects 1 product.


Products: Slideshow Project Slideshow.

## How do I fix CVE-2015-3634?

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

## Is CVE-2015-3634 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-1299](https://insights.sbomify.com/CVE-2022-1299/): Slideshow <= 2.3.1 - Admin+ Stored Cross-Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3634 and fix it if it is affected.

What it is: CVE-2015-3634 is a high-severity vulnerability in n/a, published on 8 Jun 2017. 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-2015-3634 in the wild and no public exploit code.

Affected product: n/a. 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-2015-3634/ (Markdown: https://insights.sbomify.com/CVE-2015-3634/index.md)
```

## Sources

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

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