Vulnerability in wagtail (CVE-2023-28836)

Summary

vulnerability in wagtail (CVE-2023-28836). Risk of unauthorized operations or information disclosure. Exploitable via ``ChooseParentView``. Mitigation: upgrade to `eefc3381d37b476791610e5d30594fae443f33af, bc84bf9815610cfbf8db3b6050c7ddcbaa4b9713, 5be2b1ed55fd7259dfdf2c82e7701dba407b8b62, ff806ab173a504395fdfb3139eb0a29444ab4b91, 4.1.4, 4.2.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2023-28836** has been found in wagtail. Attackers can target a specific entry point like ``ChooseParentView`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade wagtail to **eefc3381d37b476791610e5d30594fae443f33af, bc84bf9815610cfbf8db3b6050c7ddcbaa4b9713, 5be2b1ed55fd7259dfdf2c82e7701dba407b8b62, ff806ab173a504395fdfb3139eb0a29444ab4b91, 4.1.4, 4.2.2** or later. If unsure, ask your IT team or search "wagtail CVE-2023-28836" on the vendor's site.

CVE-2023-28836 (wagtail) — Attack surface: `ChooseParentView` / `InspectView` Patched: `eefc3381d37b476791610e5d30594fae443f33af, bc84bf9815610cfbf8db3b6050c7ddcbaa4b9713, 5be2b1ed55fd7259dfdf2c82e7701dba407b8b62, ff806ab173a504395fdfb3139eb0a29444ab4b91, 4.1.4, 4.2.2` — 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.

❓ What is the problem

**A vulnerability** (unclassified) exists in wagtail. Attackers reach the vulnerable code path via ``ChooseParentView`` without authentication.

📍 Affected scope

wagtail — . Attack surface: `ChooseParentView` / `InspectView`.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **eefc3381d37b476791610e5d30594fae443f33af, bc84bf9815610cfbf8db3b6050c7ddcbaa4b9713, 5be2b1ed55fd7259dfdf2c82e7701dba407b8b62, ff806ab173a504395fdfb3139eb0a29444ab4b91, 4.1.4, 4.2.2**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'wagtail' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'wagtail' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wagtail` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade wagtail to eefc3381d37b476791610e5d30594fae443f33af, bc84bf9815610cfbf8db3b6050c7ddcbaa4b9713, 5be2b1ed55fd7259dfdf2c82e7701dba407b8b62, ff806ab173a504395fdfb3139eb0a29444ab4b91, 4.1.4, 4.2.2
```
ステージング環境で eefc3381d37b476791610e5d30594fae443f33af, bc84bf9815610cfbf8db3b6050c7ddcbaa4b9713, 5be2b1ed55fd7259dfdf2c82e7701dba407b8b62, ff806ab173a504395fdfb3139eb0a29444ab4b91, 4.1.4, 4.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI wagtail

[{"repo":"https:\/\/github.com\/wagtail\/wagtail","type":"GIT","events":[{"introduced":"0"},{"fixed":"eefc3381d37b476791610e5d30594fae443f33af"},{"fixed":"bc84bf9815610cfbf8db3b6050c7ddcbaa4b9713"},{"fixed":"5be2b1ed55fd7259dfdf2c82e7701dba407b8b62"},{"fixed":"ff806ab173a504395fdfb3139eb0a29444ab4b91"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.5"},{"fixed":"4.1.4"},{"introduced":"4.2"},{"fixed":"4.2.2"}]}]