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

> Remote attackers can obtain sensitive information from the WordPress Simple Ads Manager plugin, requiring site administrators to update the plugin.

- **Severity:** Medium 5.3 (`CVSS:3.0/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:** 20 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6v95-wqcc-pxgg

## What is CVE-2015-2826?

CVE-2015-2826 is a medium-severity vulnerability in n/a, published on 20 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Simple Ads Manager plugin 2.5.94 and 2.5.96 allows remote attackers to obtain sensitive information.

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

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

It affects 1 product.


Products: Simple Ads Manager Project Simple Ads Manager.

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

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

## Is CVE-2015-2826 being exploited?

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

Public exploit code:

- WordPress Plugin Simple Ads Manager - Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-2825](https://insights.sbomify.com/CVE-2015-2825/): File upload in n/a (high 7.5)
- [CVE-2015-2824](https://insights.sbomify.com/CVE-2015-2824/): SQL injection in n/a (high 7.5)
- [CVE-2017-20095](https://insights.sbomify.com/CVE-2017-20095/): Simple Ads Manager Plugin code injection (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2826 is a medium-severity vulnerability in n/a, published on 20 Sep 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-2826 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-2826/ (Markdown: https://insights.sbomify.com/CVE-2015-2826/index.md)
```

## Sources

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

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