Security readout for executives and security teams
Plain-English summary
This affects the WordPress Custom field finder plugin through version 0.3. The issue is unsafe PHP deserialization, which can let crafted data influence application behavior. The published score is medium, but exposed WordPress sites should treat it as a cleanup priority because vulnerable plugins often become long-lived risk.
Executive priority
Prioritize identification and removal or vendor-guided remediation across WordPress estates. This is not evidenced as actively exploited in the bundle, but unresolved vulnerable plugins create avoidable exposure and should not remain unmanaged.
Technical view
CVE-2024-33641 is CWE-502 deserialization of untrusted data in Team Yoast Custom field finder. The CVSS 3.1 vector is 5.4: network reachable, high complexity, no privileges, no user interaction, changed scope, and low confidentiality and integrity impact. The bundle does not name a patched version.
Likely exposure
Exposure appears limited to WordPress installations with the Custom field finder plugin installed, especially versions through 0.3. The source bundle does not identify affected hosting platforms, themes, or downstream products beyond this plugin.
Exploitation context
The provided data does not show CISA KEV listing or other evidence of active exploitation. The high attack complexity lowers immediate likelihood, but public vulnerability cataloging can still drive opportunistic scanning for installed vulnerable plugins.
Researcher notes
Evidence is sparse. The CVE and Patchstack entry identify PHP object injection via untrusted deserialization, but the bundle does not provide exploit prerequisites, vulnerable code paths, proof of exploitation, or a specific fixed version. Avoid assuming broader Yoast product impact.
Mitigation direction
- Inventory WordPress sites for the Custom field finder plugin.
- Disable or remove the plugin if it is not business-critical.
- Check Team Yoast, WordPress.org, and Patchstack guidance for a fixed release.
- Update only to a vendor-confirmed safe version when available.
- Monitor affected sites for unusual requests or integrity changes.
Validation and detection
- Confirm whether custom-field-finder is installed on each WordPress site.
- Record the installed plugin version and flag versions through 0.3.
- Check vulnerability management tools for CVE-2024-33641 detection coverage.
- Review WordPress and web logs for suspicious plugin-targeted traffic.
- Document compensating controls if the plugin cannot be removed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-33641 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N2.22.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.