CVE-2026-55885
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGrav is a file-based Web platform. Prior to 1.7.53, an authenticated administrator with backup permissions can download a ZIP archive containing the full Grav installation root, including user/accounts/admin.yaml with the administrator password hash and user/config with site configuration, through the backup download endpoint protected only by the session-static admin-nonce URL parameter. This issue is reported as fixed in version 1.7.53.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAuthenticated administrators with backup permissions can download a full ZIP backup of the Grav installation through a vulnerable endpoint, exposing sensitive files including user/accounts/admin.yaml (containing password hashes) and user/config (site configuration). The endpoint is protected only by a session-static admin-nonce URL parameter, which is insufficient protection.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Grav CMS installationLook for Grav installation directories (e.g., /var/www/html/, /home/*/public_html/, or check your web root). Look for the presence of index.php and system/ directory containing Grav core files.Affected if Grav CMS is present in the environment
-
Identify installed Grav versionCheck the version file: open system/defines.php and look for the GRAV_VERSION constant, or check user/images/.gitignore for version comments in early Grav versions.Affected if Installed version is lower than 1.7.53 (e.g., 1.7.0 through 1.7.52)
-
Verify admin plugin is enabledCheck if the admin plugin exists and is enabled by examining user/plugins/admin/blueprints.yaml or user/plugins/enabled.yaml if present, or look for the admin plugin directory under user/plugins/.Affected if The admin plugin directory exists and is enabled, allowing admin access to the CMS
-
Check admin user backup permissionsExamine user/accounts/*.yaml files (typically user/accounts/admin.yaml) and look for the 'access' section. Check if 'admin.backup' or 'admin.maintenance' permissions are assigned to any administrator account.Affected if Any administrator account has backup or maintenance permissions enabled in their account configuration
Environment is affected if running Grav CMS version below 1.7.53 with the admin plugin enabled and at least one admin account possessing backup permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Grav to version 1.7.53 or later to apply the security patch. Additionally, review admin user permissions and audit access to backup functionality.
Grav CMS version 1.7.53
- Upgrade Grav CMS to version 1.7.53 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-55885 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data