CVE-2024-31094
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 · uneditedDeserialization of Untrusted Data vulnerability in Filter Custom Fields & Taxonomies Light.This issue affects Filter Custom Fields & Taxonomies Light: from n/a through 1.05.
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 confidenceThe Filter Custom Fields & Taxonomies Light WordPress plugin (versions up to 1.05) contains a deserialization vulnerability where untrusted data is processed without proper validation. This type of flaw can potentially allow authenticated attackers to execute arbitrary code depending on available PHP classes in the application context.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check plugin version in WordPress adminNavigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Filter Custom Fields & Taxonomies Light' and read the version number displayed below the plugin name.Affected if The listed version is 1.05 or any version number lower than 1.05.
-
Verify plugin file version headerAccess the plugin directory via FTP or file manager. Open the main plugin file (typically filter-custom-fields-taxonomies-light.php) and locate the 'Version' header comment at the top of the file.Affected if The Version header shows 1.05 or lower.
-
Confirm plugin is activeIn WordPress admin under Plugins > Installed Plugins, check whether 'Filter Custom Fields & Taxonomies Light' shows as 'Active' rather than 'Inactive' or 'Must-Use'.Affected if The plugin is active and the version is 1.05 or lower.
-
Check for authenticated user accessReview user roles and capabilities in WordPress. Determine if any user accounts exist with permissions to access plugin features that handle serialized data processing.Affected if Any authenticated user with subscriber-level or higher access exists while the vulnerable plugin version is active.
A user is affected if the Filter Custom Fields & Taxonomies Light plugin is installed at version 1.05 or below and is currently active, allowing authenticated attackers to trigger unsafe deserialization operations.
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 to the latest version of the plugin if a patch is available; otherwise disable the plugin immediately and seek an alternative solution. Verify that all deserialization operations use safe functions with proper whitelist validation.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31094 — 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-31094 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