CVE-2025-58612
BaseFortify
Publication date: 2025-09-03
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 |
|---|---|---|
| property_hive | property_hive_plugin | 2.1.5 |
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 PropertyHive Plugin versions up to 2.1.5. It allows an attacker with contributor-level privileges to inject malicious scripts, such as redirects, advertisements, or other HTML payloads, into the website. These scripts execute when visitors access the site, potentially compromising site integrity and user experience. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to inject malicious scripts into your website, which execute when visitors access it. This can lead to unwanted redirects, display of malicious advertisements, or other harmful HTML content. Although the severity is considered low and exploitation unlikely, it can still compromise the integrity of your site and negatively affect user experience. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking if the PropertyHive Plugin version is 2.1.5 or earlier, as these versions are vulnerable. There are no specific commands provided for detection in the resources. However, monitoring for unusual script injections or unexpected HTML payloads in the website content may indicate exploitation. Professional incident response and server-side malware scanning are recommended for compromise detection rather than relying on plugin-based scanners. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the PropertyHive Plugin to version 2.1.6 or later, where the vulnerability is fixed. As an interim measure, Patchstack offers virtual patching (vPatching) that automatically protects sites before official patches are applied. Additionally, timely updates are strongly advised to prevent opportunistic automated attacks. [1]