CVE-2025-58825
BaseFortify
Publication date: 2025-09-05
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| patchstack | comment_form_wp_customize_default_comment_form | 2.0.0 |
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 plugin 'Comment Form WP – Customize Default Comment Form' up to version 2.0.0. It allows an attacker with administrator privileges to inject malicious scripts into the website, which then execute when visitors access the site. These scripts can include redirects, advertisements, or other harmful HTML payloads. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can allow attackers to execute malicious scripts on your website, potentially leading to unauthorized redirects, displaying unwanted advertisements, or other harmful actions affecting visitors. Although the risk is considered low due to limited exploitability and low severity, it can still compromise user experience and site integrity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for injected malicious scripts in the Comment Form WP – Customize Default Comment Form plugin, especially in versions up to 2.0.0. Since the vulnerability allows stored XSS via administrator privileges, inspecting the comment inputs and stored comments for suspicious scripts is recommended. Specific commands are not provided in the available resources. However, administrators can review the plugin's comment data in the WordPress database for suspicious HTML or JavaScript payloads. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack, which auto-mitigates the vulnerability even without an official fix. Additionally, site administrators should monitor for suspicious activity, restrict administrator privileges carefully, and consider disabling or replacing the affected plugin until an official patch is released. [1]