CVE-2025-58874
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 | wordpress_storymap_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 Cross-site Scripting (XSS) issue in the WordPress StoryMap Plugin (versions up to 2.1). It allows an attacker with contributor-level privileges to inject malicious scripts into a 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, specifically DOM-Based XSS. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can allow attackers to run malicious scripts on your website, which may lead to unauthorized redirects, display of unwanted content, or other malicious actions affecting visitors. This can harm your site's reputation, lead to data theft, or compromise user trust. Although the risk is considered low and exploitation unlikely, attackers may opportunistically target vulnerable sites before patches or mitigations are applied. [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 WordPress StoryMap Plugin up to version 2.1, especially from users with contributor-level privileges. Since plugin-based malware scanners can be unreliable, it is recommended to perform server-side malware scanning and seek professional incident response. Specific commands are not provided in the available resources. [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 without an official fix and without performance loss. Additionally, users should monitor for suspicious activity, consider professional incident response, and perform server-side malware scanning if compromise is suspected. [1]