dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-7537

HIGH · 7.2 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
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.

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 · high confidence

The MDJM Event Management WordPress plugin lacks proper file validation in the mdjm_send_comm_email function, allowing authenticated administrators to upload arbitrary files without checking extension, MIME type, or file content. This enables uploading of executable files (e.g., PHP scripts) directly to the web root, achieving remote code execution.

MitigationUpdate the MDJM Event Management plugin to a patched version beyond 1.7.8.3 that implements proper file type validation, extension allowlisting, and MIME type verification. Until patched, restrict administrator-level access and monitor for suspicious file uploads.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify MDJM Event Management plugin is installed
    Check WordPress plugins directory at wp-content/plugins/mdjm-event-management or view installed plugins in WordPress admin under Plugins
    Affected if Plugin is present in the installation
  2. Identify installed plugin version
    View plugin details in WordPress admin (Plugins > Installed Plugins > MDJM Event Management) or read version in plugin header file mdjm-event-management/mdjm-event-management.php
    Affected if Version is 1.7.8.3 or lower
  3. Confirm mdjm_send_comm_email function is accessible
    Search plugin files for function definition: grep -r 'function mdjm_send_comm_email' in wp-content/plugins/mdjm-event-management/
    Affected if Function exists and is defined in the codebase
  4. Check administrator user access
    Review WordPress user roles under Users menu; verify which accounts have Administrator role
    Affected if Any untrusted or compromised administrator account exists

Environment is affected if MDJM Event Management plugin is installed at version 1.7.8.3 or below and the mdjm_send_comm_email function is present and accessible to administrator 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the MDJM Event Management plugin to a patched version beyond 1.7.8.3 that implements proper file type validation, extension allowlisting, and MIME type verification. Until patched, restrict administrator-level access and monitor for suspicious file uploads.

Recommended fix Moderate confidence

MDJM Event Management version 1.7.8.4 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'MDJM Event Management' plugin
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/mdjm-event-management/
  5. After updating, verify the version is 1.7.8.4 or higher under Plugins > Installed Plugins
  6. Review any uploaded files in the wp-content/uploads/mdjm-emails/ directory and remove any suspicious or unrecognized files

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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-7537 — 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-7537 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