dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32397

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-13
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
Missing Authorization vulnerability in YMC Filter & Grids ymc-smart-filter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Filter & Grids: from n/a through <= 3.5.1.

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

The YMC Filter & Grids WordPress plugin (ymc-smart-filter) through version 3.5.1 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This broken access control issue likely enables unauthorized users to access or modify filter configurations and grid settings that should require elevated privileges.

MitigationImplement proper capability checks and authorization verification on all sensitive plugin functions, particularly admin actions and AJAX endpoints. Update to the latest patched version when available and restrict plugin access to trusted administrator-level users until resolved.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify YMC Filter & Grids plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the ymc-smart-filter folder
    Affected if the ymc-smart-filter plugin folder exists in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, find the plugin in the plugins list and view the version number displayed beneath the plugin name, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if the version is 3.5.1 or any lower version number
  3. Identify publicly accessible AJAX endpoints
    Examine the plugin files for AJAX action handlers (wp_ajax_ and wp_ajax_nopriv_ hooks) and test whether these endpoints respond without authentication by inspecting the plugin code for missing capability checks before executing sensitive operations
    Affected if the plugin contains AJAX endpoints that lack proper authorization checks (missing current_user_can or capability verification)
  4. Check for misconfigured security level settings
    Access the plugin settings pages in WordPress admin and review any access control, permission, or security level configuration options for filter and grid settings
    Affected if the plugin has configuration options that allow modification of filter or grid settings without requiring elevated user privileges

The environment is affected if the YMC Filter & Grids plugin version is 3.5.1 or lower and contains AJAX endpoints or settings that allow unauthorized access due to missing capability checks.

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

Implement proper capability checks and authorization verification on all sensitive plugin functions, particularly admin actions and AJAX endpoints. Update to the latest patched version when available and restrict plugin access to trusted administrator-level users until resolved.

Recommended fix Moderate confidence

Latest version available on WordPress plugin repository (version higher than 3.5.1)

  1. 1. Log in to the WordPress admin dashboard where the YMC Filter & Grids plugin is installed.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'YMC Filter & Grids' or 'ymc-smart-filter' in the plugin list.
  4. 4. Check if an update is available. If yes, update to the latest version.
  5. 5. If no update is available through the WordPress admin, visit the official WordPress plugin repository at wordpress.org/plugins/ymc-filter-grids/ to download the latest version.
  6. 6. Deactivate and delete the current plugin, then upload and activate the latest version from the repository.
  7. 7. Verify the plugin is functioning correctly on the frontend and backend after the update.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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