The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'headline' parameter in the [shariff] shortcode in all versions up to, and including, 4.6.20 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability occurs because the plugin uses a custom wp_kses implementation with permissive allowed HTML tags, and then performs a str_replace operation that injects HTML after sanitization, allowing event handlers to be introduced through the %total placeholder in the style attribute.
The Shariff Wrapper WordPress plugin versions up to 4.6.20 contain a Stored XSS vulnerability in the 'headline' parameter of the [shariff] shortcode, exploitable by authenticated users with Contributor access or higher. Attackers can inject malicious scripts that execute when pages are accessed, due to insufficient input sanitization and improper HTML escaping.
تحتوي إضافة Shariff Wrapper للووردبريس على ثغرة Stored XSS في معامل 'headline' بسبب عدم كفاية تنظيف المدخلات والهروب من المخرجات. يمكن للمستخدمين المصرحين على مستوى المساهم أو أعلى حقن نصوص برمجية ضارة تُنفذ عند وصول المستخدمين للصفحات المصابة.
The Shariff Wrapper WordPress plugin versions up to 4.6.20 contain a Stored XSS vulnerability in the 'headline' parameter of the [shariff] shortcode, exploitable by authenticated users with Contributor access or higher. Attackers can inject malicious scripts that execute when pages are accessed, due to insufficient input sanitization and improper HTML escaping.
Update the Shariff Wrapper plugin to version 4.6.21 or later immediately. Restrict Contributor-level access to trusted users only. Implement Web Application Firewall (WAF) rules to detect and block XSS payloads. Conduct security audit of all published content for injected scripts.
قم بتحديث إضافة Shariff Wrapper إلى الإصدار 4.6.21 أو أحدث فوراً. قيّد وصول مستوى المساهم للمستخدمين الموثوقين فقط. طبّق قواعد جدار الحماية لتطبيقات الويب لكشف وحجب حمولات XSS. أجرِ تدقيقاً أماناً لجميع المحتوى المنشور للتحقق من النصوص البرمجية المحقونة.