dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 19 Jun 2026.
JceApplication · Widgetfactorylimited

CVE-2026-48907

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 2.9.99.5 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The JCE editor extension for Joomla contains an authentication bypass vulnerability that allows unauthenticated attackers to create new editor profiles. This profile creation capability can be leveraged to configure the editor to permit PHP file uploads, leading to remote code execution on the underlying server.

MitigationImmediately restrict access to the JCE editor profile creation endpoints or update to the vendor-patched version. If immediate patching is not possible, disable the JCE extension until a fix can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JceApplication
Affected:< 2.9.99.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify JCE editor extension installation
    Check your Joomla extensions directory or component list for 'JCE Editor' or 'com_jce' - look in administrator/components or inspect the database #__extensions table
    Affected if JCE Editor extension is present on the Joomla site
  2. Determine installed JCE version
    In Joomla admin, go to Components > JCE Editor > About, or inspect the manifest file at /administrator/components/com_jce/jce.xml or the version.php file within the JCE component directory
    Affected if Version number is lower than 2.9.99.5
  3. Verify unauthenticated access to JCE
    Check if the JCE editor is accessible to anonymous/guest users by reviewing Joomla user group permissions for the JCE component under System > Permissions > JCE
    Affected if Anonymous or guest user groups have access to create or edit JCE profiles
  4. Inspect existing JCE profiles for unsafe configurations
    Go to Components > JCE Editor > Profiles and review each profile's file browser settings, specifically the 'File Browser' tab and 'Upload' settings
    Affected if Any profile has PHP file types allowed or executable file extensions permitted in the upload settings
  5. Check for unauthorized newly created profiles
    Review the profile creation date in Components > JCE Editor > Profiles and compare against known administrator activity; also check #__wf_profiles table in database for unexpected entries
    Affected if New profiles exist that were not created by your administrator team

Your environment is affected if JCE Editor version is below 2.9.99.5 and the extension or its profile creation feature is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.9.99.5 or later
Fixed in 2.9.99.5
Interim mitigation

Immediately restrict access to the JCE editor profile creation endpoints or update to the vendor-patched version. If immediate patching is not possible, disable the JCE extension until a fix can be applied.

Recommended fix High confidence

JCE Editor version 2.9.99.5 or later

  1. Download the latest JCE Editor extension from the official Joomla Content Editor website (www.joomlacontenteditor.net)
  2. Log in to the Joomla Administrator panel
  3. Navigate to Extensions > Manage > Install
  4. Upload and install the updated JCE Editor package
  5. Navigate to Components > JCE Editor > Control Panel to verify the installed version is 2.9.99.5 or higher
  6. Verify that no unauthorized editor profiles have been created

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jce Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48907 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data