WordPress security changelog
MEDIUM CVE-2024-1995 Deferred

Smart Custom Fields: A security weakness

Smart Custom Fields is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Smart Custom Fields
Plugin slug
smart-custom-fields
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Mar 20, 2024
Weakness
CWE-862 — Missing Authorization

This CVE was published Mar 20, 2024 and is one of 4 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Smart Custom Fields to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Smart Custom Fields plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the relational_posts_search() function in all versions up to, and including, 4.2.2. This makes it possible for authenticated attackers, with subscrber-level access and above, to retrieve post content that is password protected and/or private.

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

References

Primary and upstream sources