CVE-2025-9334 json
Better Find and Replace <= 1.7.7 - Authenticated (Subscriber+) Limited Code Injection
published last yr. modified last mo. also EUVD-2025-38363
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-9334 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11mo ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- codesolz Better Find and Replace – AI-Powered Suggestions
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/232f3a15-3bd3-44fa-aa07-f055e8fcda88?source=cve
- plugins.trac.wordpress.org /browser/real-time-auto-find-and-replace/trunk/core/actions/RTAFAR_CustomAjax.php#L29
- plugins.trac.wordpress.org /browser/real-time-auto-find-and-replace/trunk/core/lib/Util.php#L233
- plugins.trac.wordpress.org /browser/real-time-auto-find-and-replace/trunk/core/admin/functions/DbReplacer.php#L507
- plugins.trac.wordpress.org /changeset/3389979/
Sources
- CVE List CVE-2025-9334
- NVD CVE-2025-9334
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.