CVE-2025-58875
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 |
|---|---|---|
| wordpress | wp_github_gist | * |
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 WP Github Gist Plugin versions up to 0.5. It allows attackers with contributor-level privileges to inject malicious scripts, such as redirects or advertisements, into websites using the plugin. These scripts execute when visitors access the affected site, potentially compromising user interactions. The vulnerability arises from improper neutralization of input during web page generation. [1]
How can this vulnerability impact me? :
The vulnerability can lead to attackers injecting malicious scripts into your website, which execute when visitors access your site. This can result in unauthorized redirects, display of unwanted advertisements, or other harmful HTML payloads. Such attacks can compromise user data, degrade user trust, and potentially lead to further exploitation of your website. Since the plugin is abandoned and no official fix exists, the risk remains unless mitigated by virtual patching or plugin removal. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying if the WP Github Gist plugin version 0.5 or earlier is installed and active on your WordPress site. Since the vulnerability allows stored XSS via contributor-level input, monitoring for unusual script injections or unexpected HTML payloads in posts or gists may help. However, plugin-based malware scanners may be unreliable for this vulnerability. No specific detection commands are provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing and replacing the WP Github Gist plugin with an alternative solution, as no official fix or updated version is available and the plugin is abandoned. Applying a virtual patch (vPatch) from Patchstack can provide rapid protection by auto-mitigating the vulnerability. Deactivating the plugin alone does not eliminate the risk. If compromise is suspected, seek professional incident response. [1]