CVE-2025-57932
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 |
|---|---|---|
| wordpress | powerfolio | * |
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 PowerFolio Plugin up to version 3.2.1. It allows attackers with contributor-level privileges to inject malicious scripts, such as redirects or advertisements, into web pages generated by the plugin. These scripts execute when visitors access the affected site, potentially compromising user interactions. [1]
How can this vulnerability impact me? :
The vulnerability can lead to attackers injecting malicious scripts that execute in the browsers of site visitors. This can result in unwanted redirects, display of unauthorized advertisements, or other harmful HTML payloads. Although the risk is considered low priority due to limited impact and low likelihood of exploitation, it can still compromise user experience and potentially lead to further security issues. [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 PowerFolio plugin pages, especially those that execute when visitors access the site. Since the vulnerability requires contributor-level privileges to exploit, reviewing recent contributor inputs for suspicious scripts is recommended. Additionally, using web vulnerability scanners that detect stored XSS in WordPress plugins can help identify exploitation attempts. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which provides automatic protection even without an official fix. Users should monitor for official updates or patches and consider professional incident response if a compromise is suspected. Limiting contributor-level privileges and reviewing user inputs for malicious scripts can also reduce risk. [1]