Categories
CVE-2026-54262 medium CVSS 4.3

Vulnerability in wagtail (CVE-2026-54262)

Summary

Vulnerability in wagtail (CVE-2026-54262). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.4.2 or later.

Original description

The description as published by the source.

Impact

A low-level user with the "Can submit translation" permission can create translations for any page, including those they do not have permissions for.

Patches

Patched versions have been released as Wagtail 7.0.8, 7.3.3, 7.4.2.

Workarounds

N/A

Acknowledgements

Many thanks to @devansh3008 and @alanturing881 for reporting this issue.

For more information

If you have any questions or comments about this advisory:

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-2026-54262 has been found in wagtail.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade wagtail to 7.4.2 or later.
If unsure, ask your IT team or search "wagtail CVE-2026-54262" on the vendor's site.

CVE-2026-54262 (wagtail) — CWE-280 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 7.4.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 (CWE-280) exists in wagtail.

📍 Affected scope

Check the vendor advisory for the affected versions of wagtail.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.4.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

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

  1. 1
    Identify exposure identify
    grep -r 'wagtail' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で wagtail を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade wagtail to 7.4.2

    ステージング環境で 7.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip wagtail
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.4.2"}]}]
PyPI wagtail
[{"type":"ECOSYSTEM","events":[{"introduced":"7.4"},{"fixed":"7.4.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details