Skip to main content
mySites.guru
Free Audit
CriticalPHP2Shell is fixed, but a researcher now claims six more unpatched PHP flaws. Nothing to do today, but PHP is not out of the woodsWhat to prepare
CVE-2026-48945MediumCVSS 5.3CVE published 25 June 2026Added to mySites.guru 25 June 2026

K2 (com_k2) 1.0 to 2.26 - Unauthenticated Gallery Folder Deletion, Authenticated Arbitrary File Upload (RCE), Path Traversal and Stored XSS

K2 versions 1.0 to 2.26 are affected by six issues (CVE-2026-48941, CVE-2026-48942, CVE-2026-48943, CVE-2026-48944, CVE-2026-48945, CVE-2026-48946). The most serious needs no login at all: the frontend item.checkin task accepted a sigProFolder parameter and deleted the matching folder under /media/k2/galleries/ with no authentication, no CSRF token and no ownership check, so any anonymous visitor could wipe gallery contents with a single GET request. The other five require author or administrator access that a site administrator has explicitly granted, and are remote code execution via gallery ZIP extraction (non-image files, including .php, were left in place under the publicly served gallery folder), path traversal in the attachment 'existing' field, user property mass-assignment, and stored XSS. Fixed in K2 2.27, released 7 June 2026. K2 2.28 is the current release and also contains the fix. K2 2.26 does NOT contain the fix and is affected. Note that the CVE records contradict themselves on this point: all six are titled 'K2 extension for Joomla < 2.26' while their structured affected range reads 1.0-2.26. The vendor changelog settles it, because 2.26 (31 May 2026) is a YOOtheme Pro and PHP 8 compatibility release while 2.27 is the security release that names every one of these findings.

Is my site affected?

Affected
K2 from 1.0 up to and including 2.26
Fixed in
A release after 2.26
What to do
Update K2 to the newest release from the vendor. This flaw covers versions up to 2.26, so any later release is outside it.
Check whether your sites are affected

How CVE-2026-48945 is scored

The base metrics as CISA-ADP 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.

5.3 Medium

CVSS 3.1, scored by CISA-ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A: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
PR:N Privileges required
None. No account needed
UI:N User interaction
None. Nobody has to be tricked into anything
S:U Scope
Unchanged. Contained to the extension it is in

What it does

C:L Confidentiality
Low. Some data can be read
I:N Integrity
None. Nothing can be altered
A:N Availability
None. The site stays up

Timeline

  1. 25 June 2026CVE-2026-48945 record published by its CNA
  2. 25 June 2026mySites.guru check added for K2 (from 1.0 up to and including 2.26)

Rule details

Other vulnerabilities in K2

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

K2

References

CVE-2026-48945 questions

Which versions are affected by CVE-2026-48945?
CVE-2026-48945 affects K2 from 1.0 up to and including 2.26.
How do I fix CVE-2026-48945?
Update K2 to the newest release from the vendor. This flaw covers versions up to 2.26, so any later release is outside it.
How severe is CVE-2026-48945?
CISA-ADP scores it 5.3 (Medium) under CVSS 3.1. 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 25 October 2026.