CVE-2025-57953
BaseFortify
Publication date: 2025-09-22
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 |
|---|---|---|
| 100plugins | open_user_map | * |
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 Open User Map Plugin (versions up to 1.4.14). It allows an attacker with contributor-level privileges to inject malicious scripts into the website. These scripts can execute when visitors access the site, potentially causing redirects, displaying unwanted advertisements, or executing other harmful HTML payloads. It is a DOM-Based XSS vulnerability classified under OWASP Top 10 category A3: Injection. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to inject malicious scripts that execute in the browsers of your website visitors. This can lead to unwanted redirects, display of malicious advertisements, or other harmful actions. Although the risk is considered low and exploitation unlikely, attackers may automate exploitation opportunistically. If compromised, it may require professional incident response or server-side malware scanning to address. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for malicious script injections by users with contributor-level privileges. Since the vulnerability allows injection of malicious scripts into web pages, one approach is to scan the website content and logs for suspicious HTML or JavaScript payloads. Professional incident response or server-side malware scanning is recommended, as plugin-based malware scanners may be unreliable. 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) offered by Patchstack, which auto-mitigates the vulnerability even without an official fix. Additionally, restricting contributor-level privileges to trusted users and monitoring for suspicious activity can help reduce risk. Since no official patch is available, users should consider professional incident response and server-side malware scanning if compromise is suspected. [1]