CVE-2025-12360
BaseFortify
Publication date: 2025-11-06
Last updated on: 2025-11-06
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | real-time_auto_find_and_replace | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-12360 is a vulnerability in the Better Find and Replace – AI-Powered Suggestions WordPress plugin, specifically in the rtafar_ajax() function. The issue arises because the plugin's AJAX handler allows both authenticated and unauthenticated AJAX calls but relies on capability checks and nonce verification that are either missing or insufficient. This means that authenticated users with only Subscriber-level access can trigger OpenAI API usage through this AJAX endpoint without proper authorization, potentially consuming API quota and incurring costs. The root cause is a missing or inadequate capability check on the AJAX method, allowing lower-privileged users to invoke privileged actions. [1, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing authenticated users with low-level access (Subscriber role) to misuse the plugin's AJAX functionality to trigger OpenAI API calls. This unauthorized API usage can consume your OpenAI API quota, potentially leading to unexpected costs. Although it does not directly compromise data confidentiality or availability, it can cause financial impact due to quota consumption and misuse of API resources.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring AJAX requests to the WordPress plugin's AJAX endpoint, specifically requests to the action 'rtafar_ajax'. You can look for unauthorized or suspicious AJAX calls that invoke the 'rtafar_ajax' method, especially those made by users with Subscriber-level access or unauthenticated users. On the server, you can check web server logs for POST requests to admin-ajax.php with the parameter 'action=rtafar_ajax'. For example, using command line tools: 1. To search web server logs for such requests: grep 'action=rtafar_ajax' /var/log/apache2/access.log 2. To monitor live requests: tail -f /var/log/apache2/access.log | grep 'action=rtafar_ajax' 3. To detect if unauthorized users are triggering this, correlate the IPs or user agents with known subscriber accounts or unauthenticated sessions. Additionally, inspecting the AJAX request payloads for the 'method' parameter and nonce tokens can help identify attempts to exploit the vulnerability. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Update the Better Find and Replace – AI-Powered Suggestions plugin to a version later than 1.7.7 where this vulnerability is fixed. 2. If an update is not immediately possible, restrict access to the AJAX endpoint by disabling or limiting the 'rtafar_ajax' AJAX action for unauthenticated users, for example by removing or disabling the 'wp_ajax_nopriv_rtafar_ajax' hook. 3. Implement additional server-side access controls such as firewall rules or security plugins to block suspicious AJAX requests targeting 'rtafar_ajax'. 4. Review and harden nonce verification and capability checks in the plugin code if you have development resources. 5. Monitor usage of the OpenAI API key to detect unexpected quota consumption that may indicate exploitation. [1, 3]