Grav: Admin Backup Zip File Exposes Account Credentials and Configuration Secrets

Why this deserves its current priority

CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps getgrav/grav (composer), getgrav/grav (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for getgrav/grav, getgrav/grav.
2. 2Review the reported fix. Update getgrav/grav to 1.7.53 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Jul 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Jul 14, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Jun 19, 2026

Sources and claim methodology

• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com

Related CVEs

• djust's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a public view attribute are sent to the clientSame generic ecosystem
• djust: WebSocket/runtime reconstructed request omits the client Host, causing host/subdomain TenantResolvers to misresolve the tenant on the live pathSame generic ecosystem
• djust: Unsigned client state snapshot is restored as trusted view state (privilege escalation / state injection)Same generic ecosystem
• djust: SSE sessions are not bound to the authenticated user; the client-chosen session_id is the sole authorization capability (session hijack)Same generic ecosystem
• djust has an authorization bypass on the WebSocket/SSE mount pathSame generic ecosystem
• djust has broken object-level access control (IDOR)Same generic ecosystem