dbcve.org
Fuel CmsApplication · Thedaylightstudio

CVE-2020-26167

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-04
Fix available
A fix is available. Upgrade to after 1.4.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In FUEL CMS 11.4.12 and before, the page preview feature allows an anonymous user to take complete ownership of any account including an administrator one.

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 · moderate confidence

The page preview functionality in FUEL CMS 11.4.12 and prior versions lacks proper authentication enforcement, allowing unauthenticated (anonymous) users to access this feature and manipulate it to take ownership of any user account, including administrator accounts. This represents a critical authentication bypass leading to complete account takeover.

MitigationUpgrade to FUEL CMS version 11.4.13 or later which contains the patch for this vulnerability. Until then, disable or restrict access to the page preview functionality at the web server or application level.

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
Fuel CmsApplication
Affected:<= 1.4.12

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine FUEL CMS installed version
    Locate the version file or check the admin dashboard for the CMS version information. Common locations include a version.php file or the admin footer/summary page.
    Affected if The installed version is 1.4.12 or any prior version (1.x to 1.4.12).
  2. Identify page preview endpoint accessibility
    Test accessing the page preview functionality without authentication. The typical endpoint pattern is /fuel/preview/ or similar. Attempt to access it directly from an unauthenticated browser session or via curl without providing login credentials.
    Affected if The preview page loads or responds without requiring authentication (HTTP 200 instead of redirecting to login).
  3. Verify account takeover parameter exposure
    Examine the preview functionality request parameters. Check if the preview request accepts a parameter that can be manipulated to specify a target user account (such as a user_id, created_by, or owner field).
    Affected if The preview functionality allows passing arbitrary user identifiers that could assign account ownership to an unauthenticated attacker.

If FUEL CMS version is 1.4.12 or earlier AND the page preview endpoint is accessible without authentication, the environment is vulnerable to unauthenticated account takeover.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.4.12
Interim mitigation

Upgrade to FUEL CMS version 11.4.13 or later which contains the patch for this vulnerability. Until then, disable or restrict access to the page preview functionality at the web server or application level.

Recommended fix High confidence

Fuel CMS 1.5.1

  1. 1. Backup your current Fuel CMS installation and database before making any changes
  2. 2. Download Fuel CMS version 1.5.1 from the official GitHub repository (github.com/daylightstudio/FUEL-CMS)
  3. 3. Extract the new version files and replace the existing installation files
  4. 4. Run any available database migrations if included in the update
  5. 5. Clear all cached files in the application (particularly the cache folder)
  6. 6. Verify the upgrade by logging in and testing the page preview functionality
  7. 7. Ensure all user passwords are changed, as the vulnerability allowed account takeover
Caveat Review custom modules and themes for compatibility with the 1.5.x branch before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fuel Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-26167 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-26167 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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