CVE-2025-1528

Search and filter pro <= 2.5.19 - Missing Authorization to Authenticated (Subscriber+) Post Meta Exposure

2025-03-13 16:21
Tom Broucke

Strategic Overview

Status
Patched in 2.5.20
Affected Plugin
Search & Filter Pro
Affected Version
<= 2.5.19
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-1528
View all Search & Filter Pro vulnerabilities

At a glance

CVE-2025-1528 is a medium-severity Missing Authorization vulnerability in the Search & Filter Pro WordPress plugin, affecting versions <= 2.5.19. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.5.20; sites on affected versions should update now. Disclosed March 2025, reported by Tom Broucke.

Vulnerability Overview

The Search & Filter Pro plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'get_meta_values' function in all versions up to, and including, 2.5.19. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the values of arbitrary post meta.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Search & Filter Pro <= 2.5.19 carries this weakness at get_meta_values, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Search & Filter Pro the fix is 2.5.20: builds <= 2.5.19 are affected, anything from 2.5.20 onward is not.

Remediation

Update to version 2.5.20, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Search & Filter Pro 2.5.20 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C