Exploited vulnerability

Joomla JCE Extension Unauthenticated Remote Code Execution (CVE-2026-48907)

An unauthenticated remote code execution flaw in the JCE editor extension for Joomla, versions before 2.9.99.5.

  • On CISA KEV
CVE ID
CVE-2026-48907
CVSS
10.0 Critical (CVSS v4.0, Joomla as CNA) and 9.8 Critical (CVSS v3.1, NVD primary)
CISA KEV
Listed
Affected product
Joomla Content Editor (JCE) extension for Joomla, versions before 2.9.99.5
Exploited
Yes
Published
3 June 2026 (fix released); CVE record 5 June 2026; vendor advisory page created 12 June 2026

In short

CVE-2026-48907 is an unauthenticated remote code execution flaw in the JCE editor extension for Joomla, versions before 2.9.99.5. An anonymous visitor can create an editor profile that permits uploads and then upload PHP code. The Joomla CNA rates it CVSS 4.0 10.0, and CISA added it to KEV on 16 June 2026.

Profile MapVulnerability
  1. CVECVE-2026-48907
  2. ProductWidget Factory (JCE, joomlacontenteditor.net) Joomla Content Editor (JCE) extension for Joomla, versions before 2.9.99.5
  3. CISA KEVListedKnown Exploited Vulnerabilities
  4. ExploitedYesin real attacks
  5. Fix Steps5actions listedSearch Logs and Upload Folders

What it allows

The CVE record says a flaw in the JCE editor extension for Joomla "allows the creation of new editor profiles for unauthenticated users." The result, it says, is PHP code upload and execution. The Joomla CNA rates it CVSS 4.0 10.0 Critical, and NVD adds a CVSS 3.1 score of 9.8. CISA lists it in KEV as an improper access control flaw (CWE-284).

JCE is a rich text editor that site owners install in Joomla. An editor profile controls what a group of users may do in that editor, including which file types they may upload. Letting an anonymous visitor create a profile hands that visitor the upload settings.

How the Attack Works

The vendor's advisory says the attack gets an editor profile onto the site that permits uploading executable files, then uses that profile to upload one. The known entry point is an unauthenticated request to the profile import task, index.php?option=com_jce&task=profiles.import. The advisory links to an independent analysis at mysites.guru for a fuller technical breakdown.

The vendor also says attacks are automated, so a site with no public registration is not safe. The JCE changelog describes the fix in 2.9.99.5 as "Insufficient access controls permitted unauthenticated users to upload editor profiles."

Signs a Site Was Reached

The vendor lists these checks. Look for editor profiles you did not create, often with generated names near the top of the list, or profiles that permit script uploads. Check access logs for unauthenticated requests to the profile import task, and ask the host early because logs rotate.

Then inspect the images, media and tmp folders for PHP files or names that contain "php", such as foo.php.xml. The images folder is the default upload location when a profile sets no path. The earliest log match shows when the site was first reached, which helps you choose a clean backup. Our web shell glossary entry describes what an uploaded script is used for.

Exploitation Signals for CVE-2026-48907

These are the public signals we checked on 4 November 2026. Each row names its source and date.

Exploit signals
  • CISA KEVYesAdded 16 June 2026 with a due date of 19 June; CISA lists ransomware campaign use as unknown4 Nov
  • Exploitation in CISA SSVCYesExploitation active, automatable yes, technical impact total16 Jun
  • Vendor advisoryYesThe vendor says the flaw is actively exploited, working exploit code is public and attacks are automated4 Nov
  • GitHubYes23 repositories name the CVE, created between 11 June and 2 November; their descriptions mention PoC code, scanners, a detection guide and exploit tools4 Nov
  • Brandefense BlackholeYes42 Telegram posts between 5 June and 30 October, including channels that share exploit scripts and mass exploit tools4 Nov
Verdict In CISA KEV since 16 June 2026; the vendor says it is actively exploited

The repository descriptions are the authors' own claims, and we did not run any code. Some of the Blackhole posts bundle this CVE with CVE-2026-48908, a flaw in another Joomla extension, SP Page Builder.

A remote code execution flaw on a content management system is often a first step toward a wider intrusion. See our remote code execution glossary entry and the CMS and developer tool vulnerability archive for related cases.

Who is affected

The CVE record lists JCE versions 1.0.0 to 2.9.99.4 as affected, and NVD matches every version before 2.9.99.5. The vendor says its patch covers all earlier versions. The table below follows the vendor advisory and the JCE changelog.

The free patch package comes with limits that the vendor lists. It carries none of the hardening from 2.9.99.6 onward, it is provided as is, and it does not clean a compromised site. The vendor calls it a stopgap and advises moving to a supported PHP and Joomla platform.

If a site can neither update nor use the patch, the vendor recommends uninstalling JCE. Updating closes the entry point but does not remove an existing compromise. The latest changelog entry we read is 2.9.99.12 of 7 October 2026.

The changelog also lists a separate fix in 2.9.99.10, CVE-2026-65891, which needs an authenticated, privileged user. Do not confuse the two. Our patch management glossary entry and vulnerability management guide cover how to track extension updates across many sites.

Timeline

  1. 3 Jun 2026

    JCE 2.9.99.5 is released with the fix for unauthenticated editor profile upload.

  2. 5 Jun 2026

    The Joomla CNA publishes the CVE record for versions before 2.9.99.5.

  3. 8 Jun 2026

    JCE 2.9.99.6 adds hardening across input validation, access control and file handling.

  4. 11 Jun 2026

    The first of 23 GitHub repositories naming the CVE is created.

  5. 12 Jun 2026

    The vendor creates its advisory page, which now says the flaw is actively exploited and exploit code is public.

  6. 16 Jun 2026

    CISA adds the CVE to the Known Exploited Vulnerabilities catalogue with a due date of 19 June.

  7. 8 Jul 2026

    JCE 2.9.99.9, the version the vendor recommends, is released.

What to do

  1. Update JCE to 2.9.99.9 or Later

    The vendor recommends 2.9.99.9 for every site. It needs PHP 7.4 and Joomla 3.9 or later. Updating closes the entry point but does not remove an existing compromise.

  2. Use the Free Patch Package If You Cannot Update

    For JCE 2.7.x, 2.8.x and 2.9.x on older platforms, the vendor offers a Security Patch Package. Test it on a copy first. If neither route works, uninstall JCE.

  3. Check for Rogue Editor Profiles

    Look for profiles you did not create, often with generated names near the top of the list, or profiles that permit script uploads.

  4. Search Logs and Upload Folders

    Check access logs for unauthenticated requests to the profile import task and ask your host for logs early. Inspect the images, media and tmp folders for PHP files or names such as foo.php.xml.

  5. Preserve Evidence, Clean Up and Rotate Credentials

    Keep copies of the suspect profile and files, update, then delete only the rogue profiles and files uploaded through them. Rotate administrator, database and hosting or FTP credentials, and run a server-side malware scan.

Questions

Is CVE-2026-48907 exploited?

Yes. The vendor says the flaw is actively exploited with public exploit code and automated attacks. CISA added it to KEV on 16 June 2026, and its SSVC entry records exploitation as active.

Is there a free fix for older sites?

Yes, for sites that cannot meet the PHP and Joomla requirements of 2.9.99.9. The vendor offers a free Security Patch Package for JCE 2.7.x, 2.8.x and 2.9.x, with limits it lists.

Does my Joomla site need public registration to be hit?

No. The vendor says the attacks are automated and a site with no public registration is not safe, because the entry point is an unauthenticated request.

Does updating clean an already hacked site?

No. The vendor says updating blocks the entry point but does not remove an existing compromise. Check profiles, logs and upload folders, then rotate credentials.

In our research

  1. Remote code execution (RCE) Glossary term
  2. Web shell Glossary term

Sources

  1. JCE security update and a free patch for older sites JCE (joomlacontenteditor.net)
  2. JCE editor changelog JCE (joomlacontenteditor.net)
  3. CVE-2026-48907 Record CVE Program / Joomla CNA
  4. CVE-2026-48907 NVD
  5. Known Exploited Vulnerabilities Catalog CISA