CVE-2025-23550
7.1Kemal YAZICI · Product Puller
A reflected Cross-site Scripting (XSS) vulnerability in the Kemal YAZICI Product Puller plugin allows unauthenticated attackers to execute arbitrary scripts in a user's browser.
Executive summary
The Kemal YAZICI Product Puller plugin is vulnerable to reflected Cross-site Scripting, which could allow an unauthenticated attacker to execute malicious scripts within a victim's web browser.
Vulnerability
This is a reflected Cross-site Scripting (CWE-79) vulnerability occurring due to improper neutralization of user-supplied input during web page generation. An unauthenticated attacker can trigger this flaw by enticing a user to click a crafted link, leading to script execution in the context of the user's session.
Business impact
The exploitation of this vulnerability allows an attacker to perform actions on behalf of the victim, potentially leading to session hijacking, unauthorized data access, or the redirection of users to malicious websites. While the CVSS score of 7.1 indicates a high severity, the impact is primarily focused on client-side compromise rather than direct server-side data exfiltration. Organizations relying on this plugin face reputational damage if their site is used to host or facilitate attacks against their customers.
Remediation
Immediate Action: Since no specific patch version is currently identified, users should immediately deactivate and remove the Product Puller plugin from their WordPress environments until a secure update is released by the vendor.
Proactive Monitoring: Security teams should monitor web server access logs for anomalous URL parameters containing script tags or encoded JavaScript payloads.
Compensating Controls: Deploy a Web Application Firewall (WAF) with robust XSS filtering rules to inspect incoming requests and block malicious payloads targeting the vulnerable plugin parameters.
Exploitation status
Public Exploit Available: No.
Analyst recommendation
Given the potential for unauthorized script execution and the lack of a confirmed patch, the most effective remediation is the immediate removal of the affected component. Administrators should prioritize disabling this plugin to prevent potential account compromise and maintain the integrity of their web application environment.
Sources
Originally found and disclosed by João Pedro S Alcântara (Kinorth) | Patchstack Bug Bounty Program, per the CVE Program record.