Skip to main content
← Vulnerabilities

Wagtail: Identification of documents by SHA1 hash

Exploited
No known exploitation
Fix
Fixed in 7.0.9, 7.3.4, 7.4.3, 8.0rc2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3, 8.0rc2.

Published
Last modified
13/100 · provisional
Low (ghsa)
None on Exploit-DB, Metasploit or GitHub

Summary

Wagtail, a Python content management system, has a flaw in its document serving endpoint that lets an attacker check whether a document with a given ID matches a specific SHA1 hash, regardless of permission restrictions. The attacker can only confirm a hash they already know and cannot view the document's contents or other metadata.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

Impact

By passing specific HTTP headers to the document serve URL endpoint, an attacker was able to determine whether a document with a given ID matched a specified SHA1 hash, regardless of any permission restrictions on the document or knowing its filename. This could allow an attacker to determine whether a document with a specific known hash is present in the Wagtail document library.

This vulnerability does not expose the document's contents or any metadata beyond the already known SHA1 hash, and does not expose information about any documents for which the attacker does not know the SHA1 hash.

Patches

Patched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.

Workarounds

Site owners who are unable to upgrade can strip If-Match and If-None-Match from anonymous requests to /documents/ at the reverse proxy, or use a custom document model without a file_hash attribute.

Acknowledgements

Many thanks to Anand Himanshu for reporting this issue.

For more information

If you have any questions or comments about this advisory:

  • Visit Wagtail's support channels
  • Email us at security@wagtail.org (view our security policy for more information).

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach12/20wagtail: 177.9K downloads a week
  • Severity1/10Rated low by ghsa
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Impact

  • Widely used

    wagtail has 177.9k weekly downloads.Source: pypistats.org

    410 packages depend on wagtail.Source: deps.dev

What to do

  • Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3, 8.0rc2.

Timeline

  1. Advisory published
  2. Record last updated

Affected versions

  • fixed in 7.0.9

    Fixed in 7.0.9 (released Aug 20, 2026, the day of disclosure).

  • From 7.1 · fixed in 7.3.4

    Fixed in 7.3.4 (released Aug 20, 2026, the day of disclosure).

  • From 7.4 · fixed in 7.4.3

    Fixed in 7.4.3 (released Aug 20, 2026, the day of disclosure).

  • From 8.0rc1 · fixed in 8.0rc2

    Fixed in 8.0.0rc2 (released Aug 20, 2026, the day of disclosure).

    The latest release, 8.1.0, is not affected.

Evidence 2

  1. Advisory
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about GHSA-92HV-J533-69WC

Is GHSA-92HV-J533-69WC being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by GHSA-92HV-J533-69WC?

wagtail (PyPI): before 7.0.9. wagtail (PyPI): from 7.1 before 7.3.4. wagtail (PyPI): from 7.4 before 7.4.3. wagtail (PyPI): from 8.0rc1 before 8.0rc2.Source: cve.now feed data

How do I fix GHSA-92HV-J533-69WC?

Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3, 8.0rc2.Source: cve.now feed data