Vulnerability in plone (CVE-2015-7315)
Summary
Vulnerability in plone (CVE-2015-7315). Data can be tampered with by attackers. Mitigation: upgrade to 5.0rc2 or later.
Original description
The description as published by the source.
Plone 3.3.0 through 3.3.6, 4.0.0 through 4.0.10, 4.1.0 through 4.1.6, 4.2.0 through 4.2.7, 4.3.0 through 4.3.6, and 5.0rc1 allows remote attackers to add a new member to a Plone site with registration enabled, without acknowledgment of site administrator.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2015-7315 has been found in plone.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade plone to 5.0rc2 or later.
If unsure, ask your IT team or search "plone CVE-2015-7315" on the vendor's site.
CVE-2015-7315 (plone) — CWE-284 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.0rc2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in plone.
Check the vendor advisory for the affected versions of plone.
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers.
Update to 5.0rc2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'plone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'plone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ploneを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade plone to 5.0rc2ステージング環境で 5.0rc2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web openwall.com
- web bugzilla.redhat.com
- web github.com
- web plone.org
- web github.com
- web github.com
- web github.com
- web pypi.org