CVE-2025-27358
BaseFortify
Publication date: 2025-07-04
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-80 | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Content Injection issue in the WordPress Frontend File Manager plugin (up to version 23.2) that allows a malicious user with subscriber-level access to inject arbitrary content into website pages and posts. It is related to improper neutralization of script-related HTML tags, enabling code injection which can be used to insert phishing pages or manipulate content. [1]
How can this vulnerability impact me? :
The vulnerability can allow unauthorized content manipulation on your website, including the insertion of phishing pages. This can lead to compromised website integrity, potential harm to visitors, and damage to your site's reputation. Although the severity is considered low, it still poses risks of content injection and phishing attacks. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for unauthorized content injection or manipulation in website pages and posts, especially from users with subscriber-level access. Since no official patch or specific detection commands are provided, it is recommended to perform server-side malware scanning and professional incident response to identify signs of compromise. Monitoring logs for suspicious content changes or injection attempts may also help detect exploitation. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing virtual patching (vPatching) to automatically protect against the vulnerability without waiting for an official patch. Additionally, monitoring for updates from the plugin developer is advised. Restricting subscriber-level privileges where possible and performing professional incident response and server-side malware scanning in case of suspected compromise are also recommended. [1]