dbcve.org
Better SearchWordPress extension · Webberzone

CVE-2024-29142

HIGH · 7.1 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 3.3.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WebberZone Better Search – Relevant search results for WordPress allows Stored XSS.This issue affects Better Search – Relevant search results for WordPress: from n/a through 3.3.0.

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 · high confidence

This is a Stored Cross-Site Scripting (XSS) vulnerability in the WebberZone Better Search WordPress plugin. The plugin fails to properly sanitize and escape user input (likely search terms or related data) before storing it, allowing malicious JavaScript to be persisted in the database. When other users view search result pages, the injected script executes in their browsers.

MitigationUpdate the Better Search plugin to version 3.3.1 or later to receive the vendor patch that implements proper input sanitization and output escaping.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Better SearchWordPress extension
Affected:< 3.3.1

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Check if the WebberZone Better Search plugin is present in your WordPress installation by inspecting the wp-content/plugins/better-search directory, or by running: wp plugin list --status=active --name='better-search'
    Affected if The plugin directory does not exist or the plugin is not listed in WordPress, then this CVE does not apply.
  2. Identify installed version
    Locate the main plugin file (better-search.php) and read the version string from the plugin header, or run: wp plugin get better-search --field=version
    Affected if The version is displayed as 3.3.1 or higher, then the vulnerability is patched and you are not affected.
  3. Verify active status
    Confirm the plugin is actively enabled on the site. In WordPress admin, check Plugins > Installed Plugins to see if Better Search is activated, or use: wp plugin status better-search
    Affected if The plugin is installed but not activated, the stored XSS cannot be triggered since the search functionality is not running.
  4. Check search feature usage
    Review if the search functionality is publicly accessible. Look for the Better Search widget or shortcode [better_search] being used on pages, or check the plugin settings at Settings > Better Search
    Affected if The plugin is active and version is below 3.3.1, AND the search feature is publicly accessible, then the vulnerability is present and exploitable.

You are affected if the Better Search plugin is installed, active, running version below 3.3.1, and the search functionality is enabled on your site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.3.1 or later
Fixed in 3.3.1
Interim mitigation

Update the Better Search plugin to version 3.3.1 or later to receive the vendor patch that implements proper input sanitization and output escaping.

Recommended fix High confidence

Better Search plugin version 3.3.1 or later

  1. Backup your WordPress site before performing any updates
  2. Navigate to Dashboard > Plugins in WordPress admin
  3. Locate the Better Search plugin in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 3.3.1 or later
  5. Alternatively, upload the latest version of Better Search plugin (3.3.1 or higher) via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version shows 3.3.1 or higher under Plugins > Installed Plugins
  7. Test the search functionality to ensure the plugin continues to work correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Better Search Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29142 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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