CVE-2026-7879
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 · uneditedIn Concrete CMS 9.5.0 and below, the submit_password() method in concrete/controllers/single_page/download_file.php allows unauthorized file access since downloading permission-restricted files bypasses the view_file permission check. Files without passwords can be downloaded and any user who knows a file's password can download a password protected file regardless of whether they have permission to access the file. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 6.3 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Thanks Youssef Eid for reporting
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 confidenceIn Concrete CMS 9.5.0 and below, the submit_password() method in the download_file.php controller bypasses the view_file permission check, allowing unauthorized file access. An attacker can download files without password protection or any file if they know its password, regardless of their actual file access permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.5.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify Concrete CMS versionCheck your Concrete CMS installation version (typically in dashboard or a version file) and compare it to the affected range: versions prior to 9.5.1 are vulnerableAffected if Installed version is less than 9.5.1
-
Locate the vulnerable controller fileFind the file concrete/controllers/single_page/download_file.php in your installationAffected if The file exists and is in use
-
Inspect submit_password() method for permission checkOpen the download_file.php controller and examine the submit_password() method - look for a call to a permission check (such as view_file or FilePermission) before allowing the downloadAffected if The submit_password() method does NOT call a view_file permission check before proceeding with the download
-
Verify password-protected file access controlTest that password-protected files require both correct password AND view_file permission - the method should verify actual access rights, not just accept any valid passwordAffected if Files can be downloaded with just a password without verifying the user's view_file permission
You are affected if your Concrete CMS version is below 9.5.1 AND the submit_password() method in download_file.php bypasses the view_file permission check before allowing file downloads.
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 · scoped9.5.1
Upgrade to Concrete CMS version 9.5.1 or later which includes the patched submit_password() method with proper permission verification. If immediate upgrade is not possible, restrict access to the download_file.php endpoint pending the patch.
Concrete CMS 9.5.1
- Backup the current Concrete CMS installation and database before upgrading
- Upgrade Concrete CMS to version 9.5.1 or later which contains the fix for the missing authorization vulnerability in the submit_password() method
- Verify the upgrade was successful by checking the admin dashboard
- Test that file download permissions are properly enforced after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7879 — 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-7879 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