dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-8207

HIGH · 7.0 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 →
76/100
Remediation priority · High
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 an authenticated SQL Injection vulnerability by abusing the Tracking/graphing https://github.com/GibbonEdu/core/blob/c431e25fdc874adece5d2dc7e408e9aa2d1abadb/modules/Tracking/graphing.php#L145 feature. Successful exploitation requires Teacher or higher privileges. Exploitation could result in unintended read/write activities to the underlying database.

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

Authenticated SQL Injection vulnerability in the Tracking/graphing.php module of Gibbon LMS versions prior to v30.0.01. An attacker with Teacher-level privileges can inject malicious SQL queries through the graphing feature, potentially achieving read/write access to the underlying database.

MitigationUpgrade Gibbon to version v30.0.01 or later to obtain the patched code. Alternatively, implement input validation and parameterized queries in graphing.php around line 145 if immediate upgrade is not feasible.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/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. Confirm Gibbon installation
    Locate the Gibbon installation directory and identify the installed version from version.php or a similar version file in the core directory
    Affected if The product is not Gibbon or the version cannot be determined
  2. Compare installed version to vulnerable range
    Open the version file and compare the version number to v30.0.01 - any version before v30.0.01 is affected
    Affected if Installed version is earlier than v30.0.01 (e.g., v29.0.00, v28.0.00, etc.)
  3. Verify graphing module is accessible
    Check if the Tracking/graphing module (graphing.php) exists in the modules directory and is enabled in the Gibbon module administration interface
    Affected if The graphing module exists and is enabled in the system
  4. Confirm user privilege level
    Log in as a user with Teacher or higher privileges (Teacher, Head of Year, Principal, or Administrator role) to verify the attack surface is accessible
    Affected if A user account with Teacher or higher privileges exists in the system

If Gibbon is installed with a version before v30.0.01 AND the graphing module is enabled AND at least one user has Teacher-level access, the environment is vulnerable to CVE-2026-8207.

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 obtain the patched code. Alternatively, implement input validation and parameterized queries in graphing.php around line 145 if immediate upgrade is not feasible.

Recommended fix High confidence

v30.0.01 or later

  1. 1. Identify the currently installed Gibbon version by checking the version file or administration interface
  2. 2. Create a complete backup of the Gibbon database and all application files
  3. 3. Download Gibbon v30.0.01 or later from the official GitHub repository (github.com/GibbonEdu/core)
  4. 4. Follow the official upgrade instructions in the Gibbon documentation to apply the update
  5. 5. Verify the upgrade was successful by logging in and checking the version number
  6. 6. Test the Tracking/graphing functionality to confirm the SQL injection vulnerability is resolved
Caveat Review Gibbon v30.0.01 release notes for any configuration or feature changes before upgrading

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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