Skip to main content
mySites.guru
NewAdd every Joomla and WordPress site on a WHM or cPanel server in one goSee how it works
CVE-2026-107130MediumCVSS 6.9CVE published 5 November 2026Added to mySites.guru 4 November 2026

Gridbox (com_gridbox) 2.20.4.2 - Unauthenticated File Deletion and Stored XSS in Comments and Reviews (fixed in 2.20.5.0)

Balbooa released Gridbox 2.20.5.0 on 4 November 2026 with four security fixes, rated High by the vendor: stored cross-site scripting in the Recent Comments and Recent Reviews widgets, stored cross-site scripting in individual reviews and replies, deletion of temporary comment and review attachments without path, ownership or CSRF checks, and deletion of form submission files without any authorisation check (an IDOR that the vendor says needed no login). The release also hardens CSRF and permission checks across actions that change data, file path checks, CSV exports (SQL injection and spreadsheet formula injection) and server-side validation in the store and booking apps. We confirmed the attachment deletion, CSRF and sanitisation changes by comparing the public 2.20.5.0 package with 2.20.4.2. Found by Balbooa in its own security review; CVE ids assigned through the Joomla Security Strike Team. Not a mySites.guru finding. The Joomla CNA has reserved CVE-2026-105607, CVE-2026-107129, CVE-2026-107130 and CVE-2026-107903; the records were not yet published when this rule was written, and Balbooa does not say which id is which fix. Balbooa lists Gridbox 2.20.4.2 and earlier as affected; this rule covers 2.20.4.2, and older versions are flagged by separate Gridbox rules that should also go straight to 2.20.5.0. Update to Gridbox 2.20.5.0.

Is my site affected?

Affected
Gridbox from 2.20.4.2 up to but not including 2.20.5.0
Fixed in
2.20.5.0
What to do
Update Gridbox to 2.20.5.0 or later.

How CVE-2026-107130 is scored

The base metrics as Joomla CNA published them, and what each one means for a site running an affected version. Threat and environmental metrics are left out: they describe a moment or a particular install rather than the flaw.

6.9 Medium

CVSS 4.0, scored by Joomla CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

How it is reached

AV:N Attack vector
Network. Reachable across the internet
AC:L Attack complexity
Low. Nothing to work around, it just works
AT:N Attack requirements
None. Works against any affected install
PR:N Privileges required
None. No account needed
UI:N User interaction
None. Nobody has to be tricked into anything

What it does to the site

VC:N Confidentiality
None. Nothing can be read
VI:L Integrity
Low. Some data can be altered
VA:N Availability
None. The site stays up

What it does beyond the site

SC:N Confidentiality
None. Other systems keep their data
SI:N Integrity
None. Other systems keep their integrity
SA:N Availability
None. Other systems stay up

The rule below is rated High for the set of 4 CVEs it covers together, not for this record on its own.

Timeline

  1. 4 November 2026mySites.guru check added for Gridbox (from 2.20.4.2 up to but not including 2.20.5.0)
  2. 4 November 2026We published: Gridbox 2.20.5.0 Fixes Unauthenticated File Deletion and Stored XSS
  3. 5 November 2026CVE-2026-107130 record published by its CNA

Rule details

Our disclosure post

Other vulnerabilities in Gridbox

Updating for CVE-2026-107130 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.

Gridbox

Latest safe version: 2.20.5.0

All 20 CVEs in Gridbox

References

CVE-2026-107130 questions

Which versions are affected by CVE-2026-107130?
CVE-2026-107130 affects Gridbox from 2.20.4.2 up to but not including 2.20.5.0. The fix is in 2.20.5.0.
How do I fix CVE-2026-107130?
Update Gridbox to 2.20.5.0 or later. Then confirm the installed version on the Joomla administrator's Extensions: Manage screen.
How severe is CVE-2026-107130?
Joomla CNA scores it 6.9 (Medium) under CVSS 4.0. In plain terms: reachable across the internet, no account needed and nobody has to be tricked into anything.

Running an affected version on a site you manage?

A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.

This check is part of the mySites.guru Joomla vulnerability scanner, which reads every installed extension's version on each audit. Browse the rest of the Joomla vulnerability database.

Rules current as of 9 November 2026.