Ultimate FAQ Accordion Plugin
ultimate-faqs · plugin
Known security vulnerabilities for Ultimate FAQ Accordion Plugin. Find out in seconds which version runs on your site with WP Lens.
8 known vulnerabilities
5 exploitable without logging in · 3 with public exploit code · latest Sep 23, 2026
Before you install
Use with care
- 1 record needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 2.6.0 · last updated Oct 13, 2026 · 30K+ installs
wordpress.org status checked on Nov 16, 2026
Vulnerabilities
- High 7.5
CVE-2019-17232unauthenticated
Functions/EWD_UFAQ_Import.php in the ultimate-faqs plugin through 1.8.24 for WordPress allows unauthenticated options import.
- Medium 6.5
CVE-2026-94391contributor+≤ 2.4.14
WordPress Ultimate FAQ plugin <= 2.4.14 - Cross Site Scripting (XSS) vulnerability
- Medium 6.4
CVE-2026-4336author+≤ 2.4.7
Ultimate FAQ Accordion Plugin <= 2.4.7 - Authenticated (Author+) Stored Cross-Site Scripting via FAQ Content
- Medium 6.1
CVE-2020-7107unauthenticated · needs a click
The Ultimate FAQ plugin before 1.8.30 for WordPress allows XSS via Display_FAQ to Shortcodes/DisplayFAQs.php.
- Medium 6.1
CVE-2019-17233unauthenticated · needs a click
Functions/EWD_UFAQ_Import.php in the ultimate-faqs plugin through 1.8.24 for WordPress allows HTML content injection.
- Medium 6.1
CVE-2019-15643unauthenticated · needs a click
The ultimate-faqs plugin before 1.8.22 for WordPress has XSS.
- Medium 5.7
CVE-2021-24968subscriber+→ 2.1.2
Ultimate FAQ < 2.1.2 - Subscriber+ Arbitrary FAQ Creation
- Medium 4.3
CVE-2025-67590unauthenticated · needs a click≤ 2.4.3
WordPress Ultimate FAQ plugin <= 2.4.3 - Cross Site Request Forgery (CSRF) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.