# CVE-2026-62415: Joomla Extension - joomdonation.com - Insecure default configuration Membership Pro < 4.6.2

> Unauthenticated attackers can upload media assets due to insecure default configuration in the Joomla Membership Pro extension.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-3g5h-6x8p-7rpr

## What is CVE-2026-62415?

CVE-2026-62415 is a critical vulnerability in joomdonation.com Membership Pro extension for Joomla, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla Extension - joomdonation.com - Insecure default configuration Membership Pro < 4.6.2 - The Joomla extension Membership Pro prior version 4.6.2 did by default allow unauthenticated users to upload media assets.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2026-62415?


## How do I fix CVE-2026-62415?

No fix has been published for CVE-2026-62415 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62415 being exploited?

There is no known exploitation of CVE-2026-62415 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62415 and fix it if it is affected.

What it is: CVE-2026-62415 is a critical vulnerability in joomdonation.com Membership Pro extension for Joomla, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62415 in the wild and no public exploit code.

Affected product: joomdonation.com Membership Pro extension for Joomla. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62415/ (Markdown: https://insights.sbomify.com/CVE-2026-62415/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62415
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62415
- OSV: https://osv.dev/vulnerability/CVE-2026-62415

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62415/
Summaries are generated and may contain mistakes; the official description above is the record.