dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4336

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Ultimate FAQ Accordion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via FAQ content in all versions up to, and including, 2.4.7. This is due to the plugin calling html_entity_decode() on post_content during rendering in the set_display_variables() function (View.FAQ.class.php, line 746), which converts HTML entity-encoded payloads back into executable HTML, combined with insufficient output escaping in the faq-answer.php template where the decoded content is echoed without wp_kses_post() or any other sanitization. The ufaq custom post type is registered with 'show_in_rest' => true and defaults to 'post' capability_type, allowing Author-level users to create and publish FAQs via the REST API. An Author can submit entity-encoded malicious HTML (e.g., <img src=x onerror=alert()>) which bypasses WordPress's kses sanitization at save time (since kses sees entities as plain text, not tags), but is then decoded back into executable HTML by html_entity_decode() at render time. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in FAQ pages that will execute whenever a user accesses an injected FAQ, either directly or via the [ultimate-faqs] shortcode.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Ultimate FAQ Accordion WordPress plugin (versions up to 2.4.7) has a stored XSS vulnerability where the set_display_variables() function in View.FAQ.class.php calls html_entity_decode() on FAQ content, converting entity-encoded payloads back into executable HTML. Combined with insufficient output escaping in faq-answer.php where content is echoed without wp_kses_post(), Author-level users can inject malicious scripts via the REST API that execute when users view the FAQs.

MitigationRemove or properly handle html_entity_decode() on user-submitted content and ensure all output is sanitized with wp_kses_post() or equivalent escaping functions before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin version
    Check the installed version of the Ultimate FAQ Accordion plugin in WordPress admin (Plugins > Installed Plugins) or by reading the plugin's main PHP file header
    Affected if The installed version is 2.4.7 or lower
  2. Inspect View.FAQ.class.php for html_entity_decode()
    Locate the file View.FAQ.class.php in the plugin directory and search for the set_display_variables() function; verify it contains a call to html_entity_decode() on user-submitted FAQ content
    Affected if The function html_entity_decode() is being called on FAQ content without prior sanitization
  3. Inspect faq-answer.php for missing output escaping
    Locate the file faq-answer.php in the plugin templates directory and check if FAQ content is echoed using plain echo or printf/print without wp_kses_post() or equivalent escaping
    Affected if FAQ content is output directly without wp_kses_post() or similar sanitization functions
  4. Confirm REST API accessibility for Author role
    Test if a user with Author role can access the plugin's REST API endpoints (typically /wp-json/ultimate-faq/v1/ or similar) to create or update FAQ entries
    Affected if Author-level users have REST API write access to FAQs

A user is affected if they run Ultimate FAQ Accordion version 2.4.7 or lower and the plugin's REST API allows Author-level users to create FAQs, with html_entity_decode() in the code and output lacking wp_kses_post() sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove or properly handle html_entity_decode() on user-submitted content and ensure all output is sanitized with wp_kses_post() or equivalent escaping functions before rendering.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4336 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data