CVE Tools

CVE-2026-48907

Joomla Extension - joomlacontenteditor.net - Remote Code Execution in JCE extension for Joomla < 2.9.99.5

Exploited in the wild. In CISA KEV since 2026‑06‑16. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether your Joomla site uses the Joomla Content Editor (JCE) extension and determine its current JCE version.
  2. If your JCE version is older than 2.9.99.5, plan an immediate update to the fixed release.
  3. Upgrade JCE to version 2.9.99.5 or later (the fixed version listed for this issue).
  4. If you cannot update right away, follow Joomla/JCE guidance to reduce exposure as instructed by the vendor and CISA (and treat the site as potentially compromised).

What it is

From the CVE record

A vulnerability in the JCE editor extension for Joomla allows the creation of new editor profiles for unauthenticated users, ultimately resulting in PHP code upload and execution.

In plain language

Written by AI from the record

Joomla’s JCE (Content Editor) extension has a critical flaw where an attacker with no login can upload and run malicious code on your site; if you use Joomla with JCE and it’s older than 2.9.99.5, you should act immediately—this is already being exploited.

CVE-2026-48907 is an unauthenticated remote code execution flaw in the Joomla Content Editor (JCE) extension caused by improper access control that lets an attacker create new editor profiles, which then enables PHP code upload and execution (active exploitation confirmed via CISA KEV).

If you're affected

  • Full website takeover
  • Malicious code on server
  • Customer data exposure
  • Site defacement and downtime

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS97th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2026-06-16.

US federal agencies must remediate by 2026-06-19.

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

16% chance of exploitation activity in the next 30 days, which ranks it in the 97th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Rising.

Lifecycle

16 events over 111 days, from the signal feeds we watch.

  1. EPSS band changehigh → moderateepss band change
  2. Patch availablerecord updated
  3. Analysis publishedThe other Joomla RCE: how CVE-2026-48907 turns the JCE editor into a PHP webshell
  4. EPSS band changelow → high
  5. EPSS band changelow → high
  6. EPSS band changelow → high

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Jce, not every advisory. This one: actively exploited.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store