CVE-2025-58832
BaseFortify
Publication date: 2025-09-05
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| patchstack | search_google_plugin | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the WordPress Search by Google Plugin (versions up to 1.9). It allows an attacker with administrator privileges to inject malicious scripts into the website. These scripts can execute when visitors access the site, potentially causing redirects, displaying unwanted advertisements, or other harmful HTML payloads. The vulnerability arises from improper neutralization of input during web page generation. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers with admin access to inject malicious scripts that execute in visitors' browsers. This can compromise user experience and security by causing unwanted redirects, displaying malicious advertisements, or executing other harmful actions. Since the plugin is abandoned and no official fix exists, the risk remains unless the plugin is replaced or virtual patching is applied. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the WordPress Search by Google Plugin version is up to and including 1.9, as these versions are vulnerable. Since the vulnerability involves stored XSS via administrator privileges injecting malicious scripts, inspecting the plugin version and monitoring for unusual script injections or redirects in the website content can help detect exploitation. Specific commands are not provided in the resources, but you can check the plugin version via WordPress CLI with: `wp plugin list` and look for 'search-google' plugin version. Additionally, monitoring HTTP responses for injected scripts or unusual HTML payloads may help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the vulnerable Search by Google plugin with an alternative solution, as no official fix or updated version is available due to the plugin being abandoned. Applying a virtual patch (vPatch) provided by Patchstack is recommended to protect the website from this vulnerability without impacting performance. Simply deactivating the plugin does not eliminate the risk, so urgent replacement or virtual patching is necessary to maintain site security. [1]