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

CVE-2026-25346

HIGH · 7.1 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Ays Pro FAQ Builder AYS faq-builder-ays allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects FAQ Builder AYS: from n/a through <= 1.8.2.

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 · moderate confidence

A stored Cross-site Scripting (XSS) vulnerability in the Ays Pro FAQ Builder WordPress plugin (versions <= 1.8.2) allows authenticated attackers to inject malicious JavaScript code through FAQ input fields due to improper input sanitization and output encoding.

MitigationImplement proper input validation and output escaping using WordPress sanitization functions (sanitize_text_field, wp_kses, esc_html, esc_attr) on all user-supplied input fields in the FAQ builder plugin.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Ays Pro FAQ Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ays Pro FAQ Builder' or 'FAQ Builder' by Ays Pro. Note the installed version listed.
    Affected if Plugin is installed and active with version 1.8.2 or lower
  2. Confirm plugin version
    Check the plugin version number in the plugin list or readme.txt file within the plugin directory (wp-content/plugins/ays-faq-builder or similar). Compare against the affected range: versions <= 1.8.2
    Affected if Installed version is 1.8.2 or any version lower than 1.8.2
  3. Identify FAQ input functionality access
    Check if any user role (Administrator, Editor, Author, or custom roles) has permission to create or edit FAQ items. Go to the FAQ Builder settings page and review role capabilities under the plugin settings or user role settings.
    Affected if Authenticated users with Contributor, Author, Editor, or Administrator roles can access FAQ creation or editing forms
  4. Check FAQ entry output context
    Inspect a published FAQ page or widget where FAQ entries are displayed. Right-click and view page source to see if user-supplied FAQ question/answer content is rendered with HTML entity encoding (e.g., &lt;script&gt; instead of <script>).
    Affected if FAQ content appears raw without HTML entity encoding, allowing script tags to execute in browser

User is affected if Ays Pro FAQ Builder plugin version 1.8.2 or lower is installed, active, and authenticated users can access FAQ input fields that render unescaped content on the frontend.

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

Implement proper input validation and output escaping using WordPress sanitization functions (sanitize_text_field, wp_kses, esc_html, esc_attr) on all user-supplied input fields in the FAQ builder plugin.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25346 — 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-25346 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