CVE-2025-53275
BaseFortify
Publication date: 2025-06-27
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-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 Leyka plugin up to version 3.31.9. It allows a malicious user 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. [1]
How can this vulnerability impact me? :
The vulnerability can allow attackers to inject malicious scripts that execute in the browsers of site visitors. This can lead to unwanted redirects, display of malicious advertisements, or other harmful actions. Although the risk is considered low and exploitation unlikely, automated attacks against unpatched sites are possible. If compromised, users may need professional incident response or server-side malware scanning. [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 plugin-based malware scanners can be unreliable, professional incident response or server-side malware scanning is recommended. 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 and monitoring for suspicious activity can help reduce risk. Seeking professional incident response is advised if compromise is suspected. [1]