# CVE-2026-7537: File upload in MDJM Event Management

> Administrators can upload arbitrary executable files due to missing validation, leading to remote code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2026
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-9q5q-7m8w-wgxm

## What is CVE-2026-7537?

CVE-2026-7537 is a high-severity vulnerability in MDJM Event Management, published on 6 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The MDJM Event Management plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1.7.8.3 via the mdjm_send_comm_email function. This is due to no file type, extension, or MIME type validation being performed on uploaded files. This makes it possible for authenticated attackers, with administrator-level access and above, to upload files that may be executable, which makes remote code execution possible.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-7537 being exploited?

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

Public exploit code:

- MDJM Event Management <= 1.7.8.3 - Authenticated (Administrator+) Arbitrary File Upload via 'mdjm_email_upload_file' Parameter (github_poc): https://github.com/d0n601/CVE-2026-7537

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7537 is a high-severity vulnerability in MDJM Event Management, published on 6 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7537 in the wild and no public exploit code.

Affected product: MDJM Event Management. 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-7537/ (Markdown: https://insights.sbomify.com/CVE-2026-7537/index.md)
```

## Sources

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

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