CVE-2024-39664
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 · uneditedMissing Authorization vulnerability in YMC Filter & Grids allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Filter & Grids: from n/a through 2.8.33.
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 confidenceMissing authorization vulnerability in YMC Filter & Grids WordPress plugin allows authenticated users to access functionality that should be restricted by Access Control Lists (ACLs). This broken access control flaw enables users to perform actions outside their intended permissions.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify YMC Filter & Grids is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins, or run `wp plugin list` via WP-CLI if available. Look for 'YMC Filter & Grids' in the list.Affected if The plugin is present in the WordPress installation
-
Determine installed versionOn the Plugins page in wp-admin, click 'View Details' next to YMC Filter & Grids to see the version number. Alternatively, open the main plugin file (typically /wp-content/plugins/ymc-filter-grids/ymc-filter-grids.php) and check the 'Version' field in the plugin header comment.Affected if Unable to confirm a version number
-
Compare version against 2.8.34Review the detected version number and compare it to 2.8.34. Versions below 2.8.34 are affected by this missing authorization vulnerability.Affected if Installed version is lower than 2.8.34 (e.g., 2.8.33, 2.8.30, etc.)
-
Confirm plugin is activeOn the Plugins page, verify that YMC Filter & Grids shows as 'Active' under the plugin status. Alternatively, run `wp plugin status ymc-filter-grids` via WP-CLI.Affected if Plugin is installed but not active - the vulnerability is not exploitable in this state
You are affected if YMC Filter & Grids is installed, active, and running a version lower than 2.8.34, as the missing authorization flaw only applies to the active plugin below that version.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate YMC Filter & Grids to version 2.8.34 or later to receive the authorization fix. Review user roles and permissions until the patch is applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-39664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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