# CVE-2015-7366: Cross-site request forgery in n/a

> Remote attackers can hijack user sessions to modify account settings or disable plugins via CSRF, requiring user interaction.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rjjr-365w-f42w

## What is CVE-2015-7366?

CVE-2015-7366 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 14 Oct 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in Revive Adserver before 3.2.2 allow remote attackers to hijack the authentication of users for requests that (1) perform certain plugin actions and possibly cause a denial of service (disabled core plugins) via unknown vectors or (2) change the contact name and language or possibly have unspecified other impact via a crafted POST request to an account-user-*.php script.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Revive-Adserver Revive Adserver.

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

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

## Is CVE-2015-7366 being exploited?

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

## Other vulnerabilities in Revive-Adserver Revive Adserver

- [CVE-2016-9124](https://insights.sbomify.com/CVE-2016-9124/): Security feature bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2016-9125](https://insights.sbomify.com/CVE-2016-9125/): Auth bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2017-5830](https://insights.sbomify.com/CVE-2017-5830/): Deserialization in n/a (critical 9.8)
- [CVE-2016-9470](https://insights.sbomify.com/CVE-2016-9470/): Other in Revive Adserver All versions before 3.2.5 and 4.0.0 (critical 9.0)
- [CVE-2026-50741](https://insights.sbomify.com/CVE-2026-50741/): Code injection in Adserver (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7366 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 14 Oct 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-7366 in the wild and no public exploit code.

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

## Sources

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

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