# Joomdle (com_joomdle) 1.0.2 to 3.0.1 - Insecure Default Configuration (Joomla account read and password reset) and Reflected XSS

[Joomla Vulnerability Database](https://mysites.guru/vulnerabilities/)/CVE-2026-65882

CVE-2026-65882MediumCVSS 6.1CVE published 28 July 2026Added to mySites.guru 28 July 2026

# Joomdle (com\_joomdle) 1.0.2 to 3.0.1 - Insecure Default Configuration (Joomla account read and password reset) and Reflected XSS

Joomdle bridges a Joomla site to a Moodle installation. Every release from 0.7.0 up to and including 3.0.1 ships an insecure default configuration (CVE-2026-65881): out of the box the extension exposes read access to Joomla user accounts and allows a password reset of those accounts, so anyone who can reach the integration endpoint can enumerate CMS users and take over an account without ever authenticating to Joomla. The same releases carry a reflected XSS (CVE-2026-65882) in the goto URL parameter of the Moodle wrapper endpoint. Fixed in Joomdle 3.1.1. Update to 3.1.1 or later, then review the Joomdle configuration against the vendor defaults and audit the Joomla user list for unfamiliar accounts and unexpected password changes. NOTE ON THE VERSION FLOOR: this rule starts at 1.0.2 rather than the vendor floor of 0.7.0 because the separate "Xmap - Joomdle Plugin" ships under element com\_joomdle at version 1.0.1, and match\_extension\_type is not currently enforced by the matcher; the floor keeps that sitemap plugin from being flagged. The trade-off is that a genuine Joomdle component below 1.0.2 (0.95 and earlier) is not caught by this rule.

Copy citation

## Is my site affected?

- **Affected** - Joomdle from 1.0.2 up to and including 3.0.1
- **Fixed in** - Update to 3.1.1 or later
- **What to do** - Update Joomdle to 3.1.1 or later.

[Check whether your sites are affected](https://mysites.guru/free-audit/)

## How CVE-2026-65882 is scored

The base metrics as CISA-ADP published them, and what each one means for a site running an affected version. Threat and environmental metrics are left out: they describe a moment or a particular install rather than the flaw.

6.1 Medium

CVSS 3.1, scored by CISA-ADP

`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`

### How it is reached

- **AV:N Attack vector** - Network. Reachable across the internet
- **AC:L Attack complexity** - Low. Nothing to work around, it just works
- **PR:N Privileges required** - None. No account needed
- **UI:R User interaction** - Required. Someone has to click or visit something
- **S:C Scope** - Changed. The flaw reaches past the extension it is in

### What it does

- **C:L Confidentiality** - Low. Some data can be read
- **I:L Integrity** - Low. Some data can be altered
- **A:N Availability** - None. The site stays up

The rule below is rated High for the set of 2 CVEs it covers together, not for this record on its own.

## Timeline

1.  28 July 2026CVE-2026-65882 record published by its CNA
2.  28 July 2026mySites.guru check added for Joomdle (from 1.0.2 up to and including 3.0.1)

## Rule details

High[CVE-2026-65881](https://mysites.guru/vulnerabilities/CVE-2026-65881/)[CVE-2026-65882](https://mysites.guru/vulnerabilities/CVE-2026-65882/)2026-07-28

Joomdle

Affected versions: ≥ 1.0.2 and ≤ 3.0.1

Full advisory: [www.joomdle.com](https://www.joomdle.com/)

## Other vulnerabilities in Joomdle

Updating for CVE-2026-65882 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.

### Joomdle

Latest safe version: 3.1.1

-   [CVE-2026-65881](https://mysites.guru/vulnerabilities/CVE-2026-65881/) High, from 1.0.2 up to and including 3.0.1

## References

-   [CVE-2026-65882 on cve.org (the official CVE record)](https://www.cve.org/CVERecord?id=CVE-2026-65882)
-   [CVE-2026-65882 in the NIST National Vulnerability Database](https://nvd.nist.gov/vuln/detail/CVE-2026-65882)
-   [joomdle.com](https://www.joomdle.com/)

## CVE-2026-65882 questions

Show all

Which versions are affected by CVE-2026-65882?

[CVE-2026-65882](https://mysites.guru/vulnerabilities/CVE-2026-65882/) affects Joomdle from 1.0.2 up to and including 3.0.1.

How do I fix CVE-2026-65882?

Update Joomdle to 3.1.1 or later. Then confirm the installed version on the Joomla administrator's Extensions: Manage screen.

How severe is CVE-2026-65882?

CISA-ADP scores it 6.1 (Medium) under CVSS 3.1. In plain terms: reachable across the internet, no account needed and someone has to click or visit something.

## Running an affected version 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](https://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](https://mysites.guru/joomla-vulnerability-scanner/), which reads every installed extension's version on each audit. Browse the rest of the [Joomla vulnerability database](https://mysites.guru/vulnerabilities/).

Rules current as of 14 October 2026.