CVE-2025-32123
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-04-27
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lambertgroup | html5_video_player_with_playlist_multiple_skins | to 5.3.5 (inc) |
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?
CVE-2025-32123 is a medium severity Cross Site Scripting (XSS) vulnerability in the WordPress HTML5 Video Player with Playlist & Multiple Skins Plugin (versions up to 5.3.5). It allows an attacker to inject malicious scripts, such as redirects or advertisements, into a website. These scripts execute when visitors access the compromised site. The vulnerability is classified under OWASP Top 10 A3: Injection and requires user interaction by a privileged user to be exploited. [1]
How can this vulnerability impact me? :
This vulnerability can lead to attackers injecting malicious scripts into your website, which can execute when users visit your site. This may result in unwanted redirects, display of malicious advertisements, or other harmful HTML payloads. Exploitation requires a privileged user to interact with a crafted link or page, potentially compromising site integrity and user trust. There is currently no official patch, but mitigation rules are available to block attacks targeting this vulnerability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for attempts to inject malicious scripts via the affected plugin. Since it is a reflected XSS vulnerability, you can look for suspicious HTTP requests containing script tags or typical XSS payloads targeting the plugin endpoints. Using web application firewall (WAF) logs or intrusion detection systems (IDS) with signatures for XSS can help. Specific commands depend on your environment, but for example, using curl to test for reflected script injection in URL parameters or using tools like OWASP ZAP or Burp Suite to scan the site can be effective. No exact commands are provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the mitigation rule issued by Patchstack to block attacks targeting this vulnerability until an official patch is released. Users should promptly implement this mitigation to protect their WordPress installations using the affected plugin. Additionally, restricting user input, employing a web application firewall (WAF) with XSS filtering, and educating privileged users to avoid clicking suspicious links can reduce risk. Since no official fix or patched version is currently available, these mitigations are critical. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.