CVE-2024-7630

Relevanssi <= 4.22.2 (Free) and <= 2.25.1 (Premium) - Unauthenticated Information Exposure

2024-08-15 13:29
stealthcopter

Strategic Overview

Status
Patched in 2.25.2
Affected Plugin
Relevanssi Premium
Affected Version
<= 2.25.1
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-7630
View all Relevanssi Premium vulnerabilities

At a glance

CVE-2024-7630 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Relevanssi Premium WordPress plugin, affecting versions <= 2.25.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.25.2; sites on affected versions should update now. Disclosed August 2024, reported by stealthcopter.

Vulnerability Overview

The Relevanssi – A Better Search plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 4.22.2 (Free) and 2.25.1 (Premium) via the relevanssi_do_query() due to insufficient limitations on the posts that are returned when searching. This makes it possible for unauthenticated attackers to extract potentially sensitive information from password protected posts.

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 privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Relevanssi Premium <= 2.25.1 carries this weakness at relevanssi_do_query(), and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Relevanssi Premium the fix is 2.25.2: builds <= 2.25.1 are affected, anything from 2.25.2 onward is not.

Remediation

Update to version 2.25.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Relevanssi Premium 2.25.2 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