dbcve.org
GridboxApplication · Balbooa

CVE-2026-65890

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-29
Fix available
A fix is available. Upgrade to 2.20.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 weeks old

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
Joomla Extension - balbooa.com - Unauthenticated SQL injection in Gridbox < 2.20.2 - Multiple SQLi vectors allow unauthenticated actors to inject SQL in queries.

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

Unauthenticated SQL injection vulnerability in the Gridbox Joomla extension (balbooa.com) affecting versions prior to 2.20.2. Multiple SQL injection vectors allow remote attackers to inject arbitrary SQL commands into database queries without any authentication.

MitigationUpgrade Gridbox extension to version 2.20.2 or later to patch the SQL injection vectors. If immediate patching is not possible, consider restricting access to the extension endpoints via web application firewall or network-level controls.

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
GridboxApplication
Affected:< 2.20.2

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. Confirm Gridbox extension is installed
    Access Joomla administrator panel, navigate to Extensions > Manage, and search for 'Gridbox' or 'Balbooa' to verify the extension is present in the installation.
    Affected if Gridbox extension is found in the Joomla installation
  2. Determine installed Gridbox version
    In Joomla admin, go to Components > Gridbox to view the version, or check the extension manifest file in /administrator/components/com_gridbox/ for the version number.
    Affected if Version is less than 2.20.2 or version cannot be determined
  3. Verify Gridbox component is publicly accessible
    Confirm the Gridbox component is published and accessible without authentication by checking the component state in Extensions > Components, or by attempting to access the frontend component path.
    Affected if The Gridbox component is published and exposed to unauthenticated users
  4. Check for suspicious SQL activity in logs
    Review web server access logs and database logs for unusual SQL syntax or MySQL errors in requests targeting Gridbox endpoints, particularly in query parameters.
    Affected if Unusual SQL patterns or database errors appear in logs for Gridbox requests

The environment is affected if the Gridbox extension is installed with a version below 2.20.2 and the component is publicly accessible without authentication.

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 2.20.2 or later
Fixed in 2.20.2
Interim mitigation

Upgrade Gridbox extension to version 2.20.2 or later to patch the SQL injection vectors. If immediate patching is not possible, consider restricting access to the extension endpoints via web application firewall or network-level controls.

Recommended fix Moderate confidence

Gridbox 2.20.2 or later

  1. Backup your Joomla site and database before proceeding with any updates
  2. Navigate to the Joomla Administrator panel
  3. Go to Extensions > Manage > Install
  4. Upload and install Gridbox version 2.20.2 or later from the official balbooa.com source
  5. Clear any Joomla and browser caches after the update
  6. Verify that the Gridbox component loads correctly and all pages function as expected
  7. Confirm the SQL injection vulnerability is resolved by testing the affected vectors mentioned in the advisory

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

Fix this in Gridbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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