dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1650

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 unauthorized data modification due to a missing capability check on the 'custom_fields_controller' function in all versions up to, and including, 1.7.8.1. This makes it possible for unauthenticated attackers to delete arbitrary custom event fields via the 'delete_custom_field' and 'id' parameters.

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 authorization checks on the custom_fields_controller function, allowing unauthenticated attackers to delete arbitrary custom event fields by manipulating the delete_custom_field and id parameters. This is a Broken Access Control (CWE-862) vulnerability with CVSS 5.3.

MitigationUpdate the plugin to the latest version to receive the patched code that adds capability checks to the custom_fields_controller function, or manually add WordPress capability verification (current_user_can) before allowing field deletion operations.

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

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

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. Confirm MDJM Event Management plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'MDJM Event Management' in the list. Alternatively, check the /wp-content/plugins/ directory for the mdjm-event-management folder.
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on 'View details' for MDJM Event Management to see the version number. Alternatively, check the main plugin PHP file for the Version header in the plugin comment block.
    Affected if The installed version is within any affected version range (compare against release notes or security advisories)
  3. Verify custom event fields functionality is in use
    Check if custom event fields have been created in the plugin settings: Navigate to MDJM > Settings > Custom Fields (or similar path depending on plugin version). Look for any custom field definitions listed.
    Affected if Custom event fields exist in the configuration
  4. Inspect the custom_fields_controller function for authorization checks
    Locate the plugin file containing custom_fields_controller (typically in includes/ or admin/ directories). Examine the function to verify it includes capability checks such as current_user_can or similar authorization logic before processing delete_custom_field parameter operations.
    Affected if The function lacks WordPress capability verification (current_user_can) before allowing field deletion operations

You are affected if the MDJM Event Management plugin is installed, custom event fields are configured, and the custom_fields_controller function does not verify user capabilities before processing field deletion requests.

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 plugin to the latest version to receive the patched code that adds capability checks to the custom_fields_controller function, or manually add WordPress capability verification (current_user_can) before allowing field deletion operations.

Recommended fix Moderate confidence

MDJM Event Management plugin version 1.7.9 or higher

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'MDJM Event Management' plugin
  4. Check if the current version is 1.7.8.1 or below
  5. If vulnerable, click 'Update now' to install the latest version (1.7.9 or higher)
  6. Verify the update was successful and the plugin is now at version 1.7.9 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1650 — 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-1650 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