Cross-Site Scripting (XSS) in zope2 (CVE-2009-5145)
Summary
Cross-site scripting in zope2 (CVE-2009-5145). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.12.5 or later.
Original description
The description as published by the source.
Cross-site scripting (XSS) vulnerability in ZMI pages that use the manage_tabs_message in Zope 2.11.4, 2.11.2, 2.10.9, 2.10.7, 2.10.6, 2.10.5, 2.10.4, 2.10.2, 2.10.1, 2.12.
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-2009-5145 has been found in zope2.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade zope2 to 2.12.5 or later.
If unsure, ask your IT team or search "zope2 CVE-2009-5145" on the vendor's site.
CVE-2009-5145 (zope2) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.12.5 — 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.
Cross-site scripting (XSS) (CWE-79) exists in zope2.
Check the vendor advisory for the affected versions of zope2.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 2.12.5.
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 'zope2' . 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 'zope2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
zope2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade zope2 to 2.12.5ステージング環境で 2.12.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory securityfocus.com
- advisory security-tracker.debian.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web cve.killedkenny.io
- web openwall.com
- web bugs.launchpad.net
- web github.com
- web github.com
- web security-tracker.debian.org