NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2015-7316 — plone

MEDIUMFix: plone/Products.CMFPlone@3da710a

CVE-2015-7316 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in plone. A fix is available for plone — see the affected versions and patch details below.

Plone Cross-site Scripting Vulnerability

Also known asPYSEC-2017-53
Published
Updated
Affected
6 pkgs
Patched
5 / 6
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk
0.01%0.65%1.28%1.92%0.5%1.4%May 26Sep 26Nov 26

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

6 pkgs affected
🐍plone🐍plone🐍plone🐍plone🐍plone🐍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

Plone's URL checking infrastructure includes a method for checking if URLs valid and located in the Plone site. By passing HTML into a specially crafted url containing <script, %3Cscript, javascript:, or javascript%3A, Cross-site Scripting can be achieved.

Affected Packages

6 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIplone≥ 3.3&&< 3.3.73.3.7pip install --upgrade 'plone==3.3.7'
🐍PyPIplone≥ 4.0&&< 4.0.114.0.11pip install --upgrade 'plone==4.0.11'
🐍PyPIplone≥ 4.1&&< 4.1.74.1.7pip install --upgrade 'plone==4.1.7'
🐍PyPIplone≥ 4.2&&< 4.2.84.2.8pip install --upgrade 'plone==4.2.8'
🐍PyPIplone≥ 4.3&&< 4.3.74.3.7pip install --upgrade 'plone==4.3.7'
🐍PyPIploneall versionsNo fix

Affected Products

1 product · 40 configurations
Application
ploneplone
40 versions
3.33.3.13.3.23.3.33.3.43.3.53.3.64.04.0.14.0.24.0.34.0.4

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Fix

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

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Plone's URL checking infrastructure includes a method for checking if URLs valid and located in the Plone site. By passing HTML into a specially crafted url containing `<script`, `%3Cscript`, `javascript:`, or `javascript%3A`, Cross-site Scripting can be achieved.
O3 Security · Impact-Aware SCA

Is CVE-2015-7316 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2015-7316: plone XSS — Fixed in 3.3.7