Skip to main content
mySites.guru
CriticalA PHP security release fixes two CVSS 9.2 flaws, and PHP 8.1 and older get no patchWhat it means for your site

JCE security vulnerabilities

mySites.guru tracks 3 vulnerabilities in JCE (com_jce), covering 3 CVEs. Every connected Joomla site is checked against them on each audit.

Is my site affected?

Your site is affected if it runs JCE in any of these ranges:

  • from 2.9.99.6 up to but not including 2.9.99.10
  • from 2.7.0 up to but not including 2.9.99.6
  • from 2.5.0 up to and including 2.5.2
Latest safe version
2.9.99.10 or later. No rule we check matches that release or any newer one.
What to do
Update JCE to 2.9.99.10 or later from the vendor, then confirm the installed version on the Joomla administrator's Extensions: Manage screen.

Every JCE vulnerability we track

Newest first. CVSS is the score published in each CVE record, where it has one; the severity column is the rating our check uses.

CVEAffected versionsFixed inSeverityAdded
CVE-2026-65891CVSS 6.5from 2.9.99.6 up to but not including 2.9.99.102.9.99.10Medium2026-07-29
CVE-2026-48907CVSS 10.0from 2.7.0 up to but not including 2.9.99.62.9.99.6Critical2026-06-08
CVE-2015-7339from 2.5.0 up to and including 2.5.2after 2.5.2High2020-03-09

What we check for

CriticalCVE-2026-489072026-06-08

JCE (com_jce) below 2.9.99.6 - Unauthenticated Arbitrary File Upload (RCE) and Directory Traversal

JCE versions before 2.9.99.6 are affected by critical security issues, including an unauthenticated arbitrary file upload via editor profile upload that can lead to remote code execution and full server compromise, an authenticated authorisation bypass where a user could reach an editor profile they were not assigned to, and a directory traversal that listed folder contents outside the configured directory. Both JCE Core and JCE Pro are affected on Joomla 3, 4, 5 and 6. Update to 2.9.99.6 or later via the Joomla Update Manager.

Affected versions: ≥ 2.7.0 and < 2.9.99.6

Full advisory: our disclosure post

HighCVE-2015-73392020-03-09

JCE (com_jce) 2.5.0 to 2.5.2 - Unauthenticated Arbitrary File Upload (RCE) (CVE-2015-7339)

JCE 2.5.0 to 2.5.2 allow arbitrary file upload: a .php file submitted as an image reaches /com_jce/editor/libraries/classes/browser.php and can then be executed, giving remote code execution. CVSS 8.8 (High). Update to a current JCE release. This range sits below the 2.7.0 floor of the main JCE rule, which was set to avoid matching companion plugins that report element com_jce at 1.x, so it needs its own bounded row.

Affected versions: ≥ 2.5.0 and ≤ 2.5.2

Full advisory: nvd.nist.gov

MediumCVE-2026-658912026-07-29

JCE (com_jce) 2.9.99.6 to 2.9.99.9 - Authenticated Privileged File Rename Creating a Hidden File

JCE (Joomla Content Editor) versions 2.9.99.6 through 2.9.99.9 contain a file rename flaw in the editor filesystem functions. An authenticated user with a JCE profile granting file browser access and the Rename permission could rename a file so that it became a hidden dotfile in the folder being browsed, instead of the rename being rejected as invalid. The root cause is an ordering bug: the destination name was validated before it was sanitised, and the sanitiser strips every character outside letters, marks, numbers, underscore, dot and hyphen, so a destination such as "@@@" passed validation and then reduced to an empty string. The filesystem adapter then appended the source extension to that empty name, producing a hidden file. The same release also stopped a rename silently replacing a file that already existed. Exploitation requires authentication and a privileged, file-manager-enabled profile, so this is materially less severe than the unauthenticated upload flaw fixed in 2.9.99.5 (CVE-2026-48907). Fixed in 2.9.99.10. Interim mitigation per the vendor: disable the Rename option in the settings of each file-related plugin (Image Manager, File Browser and similar) for any profile assigned to untrusted or lower-trust users. Note that 2.9.99.10 also silently hardened the upload path well beyond this one item, expanding the blocked executable extension list, adding Unicode normalisation to defeat filename bypasses, replacing a weak 5 character md5/uniqid random filename suffix with a cryptographically secure 16 character one, and removing the allowroot filesystem option.

Affected versions: ≥ 2.9.99.6 and < 2.9.99.10

Full advisory: our disclosure post

Timeline

  1. 9 March 2020Check added for CVE-2015-7339 (from 2.5.0 up to and including 2.5.2)
  2. 9 March 2020CVE-2015-7339 record published
  3. 28 May 2026We published: JCE Free/Pro 2.9.99.4 Patches Two Authenticated Vulnerabilities in Joomla's Most Popular Editor
  4. 3 June 2026We published: JCE Free/Pro 2.9.99.5 Patches an Unauthenticated File Upload in Joomla's Most-Installed Editor
  5. 5 June 2026CVE-2026-48907 record published
  6. 8 June 2026Check added for CVE-2026-48907 (from 2.7.0 up to but not including 2.9.99.6)
  7. 8 June 2026We published: JCE Pro 2.9.99.6 Is a Hardening Release After a Full Audit of Joomla's Most-Installed Editor
  8. 9 June 2026We published: A New mySites.guru Tool to Find, and Fix, the JCE Profiles Hack (June 2026)
  9. 29 July 2026Check added for CVE-2026-65891 (from 2.9.99.6 up to but not including 2.9.99.10)
  10. 29 July 2026CVE-2026-65891 record published
  11. 29 July 2026We published: JCE 2.9.99.10 Fixes Another Security Issue
  12. 20 October 2026We published: The Joomla Content Editor (JCE) Hack, Four Months On

What we have written about JCE

References

Each CVE page above links its official cve.org record and its NVD entry.

JCE vulnerability questions

Which versions of JCE are vulnerable?
mySites.guru tracks 3 vulnerabilities in JCE (com_jce). A site is affected if its installed version is in any of these ranges: from 2.9.99.6 up to but not including 2.9.99.10; from 2.7.0 up to but not including 2.9.99.6; from 2.5.0 up to and including 2.5.2.
What is the latest safe version of JCE?
2.9.99.10. Every vulnerability tracked here is fixed by 2.9.99.10, and no rule we check matches that release or any later one.
How do I check which version of JCE my Joomla site runs?
The installed version is listed on the Joomla administrator's Extensions: Manage screen; search it for com_jce. mySites.guru reads the installed version on every audit of a connected site and checks it against these rules.

Running JCE 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.

CVE identifiers: CVE-2026-48907, CVE-2015-7339, CVE-2026-65891. Rules current as of 23 October 2026.