Widget Factory Joomla Content Editor Improper Access Control Vulnerability (CVE-2026-48907)
Published Last modified In CISA KEV since Sources: BSI, CVE.org, pwn.watch
What is affected, what to do
A critical improper access control vulnerability in JCE (Joomla Content Editor) by Widget Factory Limited allows unauthenticated remote attackers to fully compromise affected systems, impacting confidentiality, integrity, and availability. The flaw is actively exploited in the wild and has been added to the CISA Known Exploited Vulnerabilities catalog, signaling confirmed weaponization. The attack requires no privileges and no user interaction, making mass exploitation straightforward. Organizations running Joomla installations with the JCE editor plugin must immediately verify exposure and apply available patches. Given the combination of active exploitation, network-accessible attack surface, and maximum severity ratings, this vulnerability demands the highest remediation priority.
The vulnerability is being actively exploited; treat it as a priority. Update jce to version 2.9.99.5, Joomla Content Editor to version 2.9.99.5. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- Joomlacontenteditor.net Joomla Content Editor (JCE) extension for Joomla
eq 1.0.0-2.9.99.4..1.0.0-2.9.99.4
- Joomlacontenteditor.net Joomla Content Editor (JCE) extension for Joomla
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
10.0
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v4
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: BSI, CVE.org, pwn.watch
85.4 %
EPSS score
High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
Source: FIRST EPSS, percentile 99.72
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 248.07 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 10.0 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 10.0
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 85.4 %
- High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 99.72
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossaryCWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-284
Response and mitigation
Why act now?
Prioritisation rationale
This flaw is network-reachable, requires no authentication and no user interaction, and leads directly to remote PHP code execution as the webserver user — placing it in the most critical CVSS class. CISA-KEV listing confirms active exploitation and EPSS puts it in the top exploitation-likelihood percentile; opportunistic botnet and crypto-miner operators routinely sweep Joomla sites within hours of such disclosures. Target profile is every internet-exposed Joomla site running JCE below 2.9.99.5 — SMB sites, associations, municipal portals, and secondary KRITIS web presences that typically lag on patch cycles. For NIS2-regulated organisations: any perimeter JCE instance is a P1 pre-incident — patch or take down within 24 hours and follow up with a full compromise assessment of the host.
Runbook step 1
Immediate response (0-24 h)
- Upgrade the JCE extension to version 2.9.99.5 or later immediately (Joomla Administrator → Extensions → Manage → Update). The vendor patch from widgetfactorylimited covers all versions in the 1.0.0-2.9.99.4 range.
- Until patched: block the
com_jcecomponent at the reverse proxy or WAF for unauthenticated requests, specifically/index.php?option=com_jce*and any direct calls to/components/com_jce/editor/and/plugins/editors/jce/. - Audit Joomla upload directories (
/images/,/media/,/tmp/) for newly created.php,.phtml,.phar,.php7,.pht,.incfiles within the last 90 days; forensically preserve suspicious files before deletion. - Enumerate all Super User and admin accounts on affected Joomla instances for unexpected additions, rotate passwords, and invalidate API tokens and session cookies.
- Isolate internet-facing Joomla sites with JCE as a priority (temporary maintenance mode via
.htaccessIP allow-list) if the patch cannot be rolled out within 4 hours. - Open an incident ticket referencing CVE-2026-48907 with scope = all Joomla hosts; reconcile the asset inventory against
administrator/manifests/files/jce.xmlto pin exact versions.
Runbook step 2
Mitigation layers
- WAF rule: drop HTTP requests carrying
option=com_jcecombined withtask=plugin,plugin=imgmanager,method=form, oraction=uploadwhen no valid Joomla session cookie is present. Additionally rejectmultipart/form-datauploads whose filename matches\.(php[0-9]?|phar|phtml|pht|inc)$. - Web server hardening: disable PHP execution in writable paths — Apache
php_admin_flag engine offfor/images/,/media/,/tmp/,/cache/; Nginxlocation ~* /(images|media|tmp)/.*\.php$ { deny all; }. - Network segmentation: place Joomla hosts in a dedicated DMZ, enforce default-deny egress so reverse shells cannot phone home to arbitrary external IPs; allow only well-defined destinations (updates, SMTP relay).
- Filesystem controls: mount webroot read-only where possible, mount upload directories with
noexec; separate the webserver user from the Joomla file owner. - IAM: restrict
/administrator/to a dedicated admin VLAN or VPN, front with mTLS or HTTP Basic Auth, enforce MFA via a Joomla MFA plugin for all backend accounts. - IPS/IDS: enable Snort/Suricata signatures targeting JCE upload exploitation (Emerging Threats
ET WEB_SPECIFIC_APPS JCEfamily) and keep the ET feed current.
- WAF rule: drop HTTP requests carrying
Runbook step 3
Detection rules
- Web access logs: POST to
/index.phpwith queryoption=com_jceand HTTP 200, followed within 5 minutes by creation of a new.phpfile under/images/or/media/. KQL shape:W3CIISLog | where csUriQuery has "com_jce" and csMethod == "POST" | join (FileCreationEvents | where FileName endswith ".php") on $left.cIP == $right.InitiatingProcessAccountName. - Sysmon EID 11 (File Create) inside the Joomla webroot for
.php,.phar,.phtmlwhere parent process isw3wp.exe,php-fpm,httpd, orapache2. - Linux auditd watch on the webroot (
-w /var/www -p wa -k joomla_write), alerting on create events withcomm=php-fpmand PHP extensions outside core paths. - EDR process ancestry:
php-fpmorapache2spawningsh,bash,python,perl,nc,curl,wgetwith an outbound network connection — the canonical webshell pivot pattern. - Sigma shape:
detection: selection: web.request.uri_query|contains: "com_jce" web.request.method: POST web.response.status: 200 condition: selection | count() by src_ip > 5 within 1mto catch exploit scanning. - Joomla DB query:
SELECT * FROM #__users WHERE registerDate > NOW() - INTERVAL 90 DAY AND block = 0to surface unexpected admin or editor accounts.
- Web access logs: POST to
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
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.
Source: BSI CSAF, BSI WID Portal, cvelistv5, pwn.watch, CISA KEV Catalog, NVD (NIST)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| joomlacontenteditor.net | Joomla Content Editor (JCE) extension for Joomla |
|
|
| widgetfactorylimited | jce |
|
|
| Widget Factory | Joomla Content Editor |
|
|
Vendors and products
Weakness classes (CWE)
CWE-284Improper Access Control
Pillar
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Entry at MITRE CWE-284
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited | |
| PoC-in-GitHub (nomi-sec) | JCEzploit-CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907_PoC (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907-Joomla-JCE-RCE (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | Joomla_CVE_2026_48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | masta-cve-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | joomla-jce-cve-2026-48907-detection (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-48907-Unauthenticated-RCE-in-JCE (opens in a new tab)github.com | PoC (publicly reported)reported, not verified |
References & sources
- joomlacontenteditor.netProduct
- joomlacontenteditor.netWidget Factory Joomla Content Editor — CVE-2026-48907Vendor advisory, pwn-watch
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-48907government-resource
- pwn.watchpwn.watch: Widget Factory Joomla Content Editor : Widget Factory Joomla Content Editor Improper Access Control Vulnerabilitypwn-watch
- NVD (NIST)NVD: CVE-2026-48907pwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
CISA KEV entry updated9119a7d8…
4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Date Added added —2026-06-16Due Date added —2026-06-16Required Action added —2026-06-16Vulnerability Name added —2026-06-16Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725
One NVD translation into another language is hidden.
Linked advisories
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-48907"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-48907.svg?lang=en" alt="CVE-2026-48907 – NEOSEC Intel" height="20"></a>