Skip to main content
mySites.guru
CriticalPHP2Shell is fixed, but a researcher now claims six more unpatched PHP flaws. Nothing to do today, but PHP is not out of the woodsWhat to prepare

JEM - Joomla Event Manager security vulnerabilities

mySites.guru tracks 1 vulnerability in JEM - Joomla Event Manager (com_jem), covering 5 CVEs. Every connected Joomla site is checked against it on each audit.

Is my site affected?

Your site is affected if it runs JEM - Joomla Event Manager in this range:

  • before 5.0.1
Latest safe version
5.0.1 or later. No rule we check matches that release or any newer one.
What to do
Update JEM - Joomla Event Manager to 5.0.1 or later from the vendor, then confirm the installed version on the Joomla administrator's Extensions: Manage screen.

Every JEM - Joomla Event Manager 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-77034CVSS 6.9CVE-2026-77035CVSS 5.1CVE-2026-77989CVSS 5.3CVE-2026-77990CVSS 5.3CVE-2026-77991CVSS 9.4before 5.0.15.0.1Critical2026-08-27

What we check for

JEM - Joomla Event Manager (com_jem) below 5.0.1 - Privileged Remote Code Execution, Unauthenticated Article Overwrite and Force-Publish, Cross-User Event and Venue Takeover, Reflected XSS and Attendee Data Disclosure

JEM (Joomla Event Manager) by the JEM Community is affected by multiple vulnerabilities confirmed live against JEM 5. The Joomla Security Strike Team assigned five CVE IDs on 22 August 2026 and published all five records on 27 August 2026: CVE-2026-77991, CVE-2026-77034, CVE-2026-77035, CVE-2026-77989 and CVE-2026-77990. Every record gives the affected range as 1.0.0 to 5.0.0. There is still no stable version to update to. The fixes exist only in a public 5.0.1 release candidate (the 5.0.1-bugfixes branch on GitHub). The newest stable release remains 5.0.0-stable, from 8 July 2026, which is affected. Confirmed issues: (1) Privileged remote code execution (CVE-2026-77991, CVSS 9.4 Critical) - the administrator source model writes dangerous file types including PHP, giving code execution to an account that already holds administrator access. (2) Unauthenticated article overwrite and force-publish (CVE-2026-77034, CVSS 6.9) - the front-end event.updateAssociatedArticle task performs no ACL check before writing a Joomla content article, so any visitor holding their own session token can republish and overwrite an article associated with an event, including publishing an unpublished one. (3) Cross-user event and venue takeover (CVE-2026-77035, CVSS 5.1) - allowEdit() trusts jform[created_by] and jform[access] from POST data, so a registered user with edit-own rights (the eventowner=1 setting or core.edit.own) can POST another user's record id together with their own id as created_by and take over that record. (4) Reflected XSS via the PDF export link (CVE-2026-77989, CVSS 5.3) - buildCurrentPdfLink copies the current request query string into the PDF button URL and pdfbutton() echoes it unescaped (attribute injection, no tags required). (5) Attendee data disclosure (CVE-2026-77990, CVSS 5.3) - any logged-in non-manager can read attendee names, usernames, registration dates and statuses for events they do not manage, including lists belonging to unpublished events. One further item found by code reading, stored XSS through unescaped category names, has no CVE. Mitigation until 5.0.1 stable ships: restrict front-end event and venue editing and the front-end attendees view to trusted users only, consider disabling front-end event submission, and review who holds administrator access on the site given the source-model file write. Update to JEM 5.0.1 or later as soon as a stable release is available. This rule flags every JEM version below 5.0.1, which matches the affected range stated in all five CVE records.

Affected versions: < 5.0.1

Full advisory: our disclosure post

Timeline

  1. 22 August 2026We published: Five Security Issues in JEM (Joomla Event Manager), and No Stable Fix Yet
  2. 27 August 2026Check added for CVE-2026-77034, CVE-2026-77035, CVE-2026-77989, CVE-2026-77990 and CVE-2026-77991 (before 5.0.1)
  3. 27 August 2026CVE-2026-77034 record published
  4. 27 August 2026CVE-2026-77035 record published
  5. 27 August 2026CVE-2026-77989 record published
  6. 27 August 2026CVE-2026-77990 record published
  7. 27 August 2026CVE-2026-77991 record published

What we have written about JEM - Joomla Event Manager

References

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

JEM - Joomla Event Manager vulnerability questions

Which versions of JEM - Joomla Event Manager are vulnerable?
mySites.guru tracks one vulnerability in JEM - Joomla Event Manager (com_jem). A site is affected if its installed version is in this range: before 5.0.1.
What is the latest safe version of JEM - Joomla Event Manager?
5.0.1. Every vulnerability tracked here is fixed by 5.0.1, and no rule we check matches that release or any later one.
How do I check which version of JEM - Joomla Event Manager my Joomla site runs?
The installed version is listed on the Joomla administrator's Extensions: Manage screen; search it for com_jem. mySites.guru reads the installed version on every audit of a connected site and checks it against this rule.

Running JEM - Joomla Event Manager 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-77034, CVE-2026-77035, CVE-2026-77989, CVE-2026-77990, CVE-2026-77991. Rules current as of 25 October 2026.