The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via double HTML-entity encoding in all versions up to, and including, 1.32.0. This is due to the plugin's sanitization function calling `html_entity_decode()` before `wp_kses()`, and then calling `html_entity_decode()` again on output. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the 'name_directory_name' and 'name_directory_description' parameters in the public submission form granted they can trick the site administrator into approving their submission or auto-publish is enabled.
The Name Directory WordPress plugin versions up to 1.32.0 contain a Stored Cross-Site Scripting vulnerability due to improper double HTML-entity encoding in sanitization functions. Unauthenticated attackers can inject malicious scripts through public submission forms that execute when users access affected pages.
تحتوي إضافة Name Directory لـ WordPress على ثغرة Stored XSS تنتج عن استدعاء دالة html_entity_decode() قبل wp_kses() ثم استدعاؤها مرة أخرى عند الإخراج. يمكن للمهاجمين غير المصرحين حقن نصوص برمجية عشوائية عبر نماذج الإرسال العام في معاملات 'name_directory_name' و 'name_directory_description'.
The Name Directory WordPress plugin versions up to 1.32.0 contain a Stored Cross-Site Scripting vulnerability due to improper double HTML-entity encoding in sanitization functions. Unauthenticated attackers can inject malicious scripts through public submission forms that execute when users access affected pages.
Update the Name Directory plugin to version 1.32.1 or later immediately. Disable auto-publish functionality for submissions if not required. Implement strict content moderation by reviewing all pending submissions before approval. Consider using Web Application Firewall (WAF) rules to detect and block XSS payloads in submission parameters.
قم بتحديث إضافة Name Directory إلى الإصدار 1.32.1 أو أحدث فوراً. عطّل وظيفة النشر التلقائي للمساهمات إن لم تكن مطلوبة. طبّق مراجعة صارمة للمحتوى بفحص جميع المساهمات المعلقة قبل الموافقة عليها. استخدم قواعد جدار الحماية لتطبيقات الويب لكشف وحجب حمولات XSS.