How severe is CVE-2015-7293?

CVE-2015-7293 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-7293?

CVE-2015-7293 affects the following packages: plone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-7293?

Update plone to 5.0a1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-7293 is resolved across your whole dependency graph.

How do I detect CVE-2015-7293 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-7293 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2015-7293 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2015-7293, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-7293?

CVE-2015-7293 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-7293?

CVE-2015-7293 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-7293 published, and has it been updated?

CVE-2015-7293 was published on May 17, 2022 and was last updated on October 18, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2015-7293 — plone

HIGH

CVE-2015-7293 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in plone. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for plone — see the affected versions and patch details below.

Plone vulnerable to cross-site request forgery

Also known asPYSEC-2017-51

Published

May 17, 2022

Updated

Oct 18, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍plone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`plone`	all versions	5.0a1`pip install --upgrade 'plone==5.0a1'`

Affected Products

2 products · 47 configurations

Application

ploneplone

46 versions

3.33.3.13.3.23.3.33.3.43.3.53.3.64.04.0.14.0.24.0.34.0.4

Application

zope management interfacezope

≤ 4.3.7

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-38411webappspython

Zope Management Interface 4.3.7 - Cross-Site Request Forgery

by hyp3rlinx · Oct 7, 2015

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update plone to 5.0a1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-7293 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2015-7293 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No Nuclei template or Metasploit module yet. 3 public proof-of-concept references are listed on this page.

Timeline

First exploit

Oct 7, 2015

Disclosed

May 17, 2022

Last updated

Oct 18, 2024

Identifiers

CVE-2015-7293

PYSEC-2017-51

References

Advisorynvd.nist.gov · CVE 2015 7293 Webgithub.com · PYSEC 2017 51.yaml Webplone.org Webpypi.python.org · plone4.csrffixes Webexploit-db.com Webhyp3rlinx.altervista.org · AS ZOPE CSRF.txt Webpacketstormsecurity.com · Zope Management Interface 4.3.7 Cross Site Request Forgery Packagegithub.com · Plone

Related vulnerabilities

Also affects plone

This CVE is high severity — higher than any of the other 4 CVEs affecting plone (highest there: moderate).

CVE-2021-29002CVE-2011-1340CVE-2008-1396CVE-2006-1711

Same weakness: CWE-352

This CVE is high severity; 1 of 4 other CVEs with CWE-352 is rated as high or higher (top: high).

CVE-2026-96629CVE-2026-118266CVE-2026-113796CVE-2026-84312Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 18, 2024

CVE-2015-7293 — plone

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2015-7293 in your dependencies?