dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-9334

HIGH · 8.8 CVSS v3.1 Published 2025-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The Better Find and Replace – AI-Powered Suggestions plugin for WordPress is vulnerable to Limited Code Injection in all versions up to, and including, 1.7.7. This is due to insufficient input validation and restriction on the 'rtafar_ajax' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to call arbitrary plugin functions and execute code within those functions.

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

The Better Find and Replace – AI-Powered Suggestions WordPress plugin versions up to 1.7.7 contains an authenticated code injection vulnerability in the 'rtafar_ajax' function. Insufficient input validation and missing access control allows any authenticated user with Subscriber-level access or higher to call arbitrary plugin functions, leading to code execution.

MitigationUpdate the plugin to version 1.7.8 or later which addresses the input validation and access control issues in the 'rtafar_ajax' function.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify plugin installation and version
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, locate 'Better Find and Replace - AI-Powered Suggestions' and check the version number displayed. Alternatively, inspect the plugin main file (typically better-find-and-replace/better-find-and-replace.php) and look for the Version header in the plugin comments.
    Affected if The displayed version is 1.7.7 or lower.
  2. Confirm vulnerable function exists
    Access the plugin files via file manager or FTP, navigate to the plugin directory, and search for the 'rtafar_ajax' function definition in the source code files.
    Affected if The function 'rtafar_ajax' is present in the plugin code.
  3. Check WordPress user roles
    Go to WordPress admin dashboard > Users section and review the list of existing user accounts and their assigned roles.
    Affected if Any user account exists with the role of Subscriber or higher (including Contributor, Author, Editor, Administrator).

All three conditions must be true for the environment to be affected: the plugin version is 1.7.7 or lower, the rtafar_ajax function exists in the code, and at least one user with Subscriber-level access or higher is present.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.7.8 or later which addresses the input validation and access control issues in the 'rtafar_ajax' function.

Recommended fix Moderate confidence

Version 1.7.8 or later of the Better Find and Replace – AI-Powered Suggestions plugin

  1. Backup your WordPress database and files before making any changes
  2. Update the Better Find and Replace – AI-Powered Suggestions plugin to version 1.7.8 or later via WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository)
  3. Verify the update was successful by checking the plugin version in Plugins list
  4. Test that the plugin functionality works correctly after the update
  5. Ensure all users with Subscriber-level or higher access are trusted, as this vulnerability can be exploited by any authenticated user

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9334 — 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-2025-9334 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