dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-8208

HIGH · 8.9 CVSS v4.0 Published 2026-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
Gibbon versions before v30.0.01 are affected by a local file inclusion vulnerability resulting in RCE by changing the report archive directory and forcing interpretation of a user provided .zip as PHP. Successful exploitation requires Teacher or higher privileges. Exploitation could result in compromise of the underlying web server.

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 confidence

Gibbon CMS versions before v30.0.01 contain a local file inclusion vulnerability allowing authenticated users with Teacher privileges or higher to achieve remote code execution. Attackers manipulate the report archive directory path and upload a malicious .zip file that gets interpreted as PHP code, compromising the web server.

MitigationUpgrade Gibbon to version v30.0.01 or later to patch the local file inclusion vulnerability. Limit Teacher-level privileges to trusted users only until the upgrade is applied.

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
High
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify Gibbon installation
    Locate the Gibbon installation directory and find the version file (typically version.php in the root directory or Gibbon.php containing the version constant)
    Affected if Gibbon is installed and the version cannot be determined or is below v30.0.01
  2. Determine installed version
    Open the version file and locate the version number (e.g., $version = '30.0.00' or similar)
    Affected if The version string shows a release before v30.0.01 (e.g., v30.0.00, v29.0.x, etc.)
  3. Verify report module is enabled
    Access the Gibbon admin panel and check System Admin > Module Manager to confirm the Reports module is installed and enabled
    Affected if The Reports module is present and enabled in the system
  4. Confirm privilege level
    Check if any user accounts have Teacher privileges or higher by reviewing the admin panel under People > Staff or User Admin > Manage Users
    Affected if There exists at least one user account with Teacher, Coordinator, Principal, or Administrator role

If Gibbon is installed with a version before v30.0.01, the Reports module is enabled, and an account with Teacher privileges or higher exists, the environment is vulnerable to CVE-2026-8208.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Gibbon to version v30.0.01 or later to patch the local file inclusion vulnerability. Limit Teacher-level privileges to trusted users only until the upgrade is applied.

Recommended fix High confidence

v30.0.01

  1. 1. Backup your current Gibbon installation and database before proceeding with any upgrade.
  2. 2. Download Gibbon v30.0.01 or later from the official Gibbon GitHub repository or distribution channel.
  3. 3. Replace the existing Gibbon files with the new version, preserving your configuration and any custom modifications.
  4. 4. Verify that the file inclusion vulnerability in the report archive functionality has been addressed by reviewing the changelog or commit history for v30.0.01.
  5. 5. Ensure that the web server has appropriate file permissions and that user-uploaded files are stored outside the web root.
  6. 6. Test the application functionality, particularly the report archive feature, to confirm normal operation.
  7. 7. Review user accounts with Teacher privileges to ensure only authorized personnel have access.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8208 — 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-2026-8208 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