# CVE-2015-7293: Plone vulnerable to cross-site request forgery

> Attackers can perform unauthorized actions on behalf of authenticated users in Plone and Zope Management Interface via CSRF.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p3qm-44cf-f8qx, PYSEC-2017-51

## What is CVE-2015-7293?

CVE-2015-7293 is a high-severity vulnerability in Plone Plone, published on 25 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in Zope Management Interface 4.3.7 and earlier, and Plone before 5.x.

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

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

3 open source packages ship an affected version, including plone and Plone. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `plone` | PyPI | All versions | 5.0a1 |
| `plone` | PyPI | All versions | 5.0a1 |
| `Plone` | PyPI | All versions | 5.0a1 |

Products: Plone Plone, Zope Zope Management Interface.

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

Upgrade plone to 5.0a1 or later.

## Is CVE-2015-7293 being exploited?

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

Public exploit code:

- Zope Management Interface 4.3.7 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in Plone Plone

- [CVE-2021-33509](https://insights.sbomify.com/CVE-2021-33509/): Incorrect Permission Assignment for Critical Resource in Plone (critical 9.9)
- [CVE-2020-35190](https://insights.sbomify.com/CVE-2020-35190/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-7941](https://insights.sbomify.com/CVE-2020-7941/): Plone Unauthenticated Write Vulnerability (critical 9.8)
- [CVE-2011-3587](https://insights.sbomify.com/CVE-2011-3587/): Zope Command Execution Vulnerability (critical 9.3)
- [CVE-2021-33926](https://insights.sbomify.com/CVE-2021-33926/): Server-Side Request Forgery in Plone CMS (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7293 is a high-severity vulnerability in Plone Plone, published on 25 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-7293 in the wild and no public exploit code.

Affected packages and fixed versions:
- plone (PyPI): affected all versions; fixed in 5.0a1
- plone (PyPI): affected all versions; fixed in 5.0a1
- Plone (PyPI): affected all versions; fixed in 5.0a1

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-7293/ (Markdown: https://insights.sbomify.com/CVE-2015-7293/index.md)
```

## Sources

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

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