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

CVE-2026-4075

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-26
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 BWL Advanced FAQ Manager Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'baf_sbox' shortcode in all versions up to and including 1.1.1. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes such as 'sbox_id', 'sbox_class', 'placeholder', 'highlight_color', 'highlight_bg', and 'cont_ext_class'. These attributes are directly interpolated into HTML element attributes without any esc_attr() escaping in the baf_sbox() function. 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.

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 BWL Advanced FAQ Manager Lite WordPress plugin fails to escape shortcode attributes in the baf_sbox() function. Attributes like sbox_id, sbox_class, placeholder, highlight_color, highlight_bg, and cont_ext_class are directly inserted into HTML element attributes without esc_attr() sanitization, allowing stored XSS injection.

MitigationUpdate to a patched version of the plugin that applies proper esc_attr() escaping to all shortcode attributes before HTML interpolation. Until then, limit contributor-level access and review existing pages using the baf_sbox shortcode.

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 BWL Advanced FAQ Manager Lite plugin is installed
    Navigate to WordPress admin > Plugins and look for 'BWL Advanced FAQ Manager Lite' in the installed plugins list
    Affected if The plugin is installed and activated
  2. Identify the installed plugin version
    In the Plugins page, click on the plugin name or view details to see the installed version number
    Affected if The version number is lower than the patched version (update to latest to determine)
  3. Find usage of the baf_sbox shortcode
    Search your WordPress posts, pages, and custom post types for the shortcode [baf_sbox] or its variants containing sbox_id, sbox_class, placeholder, highlight_color, highlight_bg, or cont_ext_class attributes
    Affected if The shortcode is present and contains any of these attributes: sbox_id, sbox_class, placeholder, highlight_color, highlight_bg, cont_ext_class
  4. Inspect shortcode attribute values in the database
    Query the wp_posts table for content containing 'baf_sbox' and examine the attribute values assigned to sbox_id, sbox_class, placeholder, highlight_color, highlight_bg, and cont_ext_class
    Affected if Any of these attributes contain unescaped HTML special characters (<, >, ", ') that could execute as XSS when the shortcode renders
  5. Verify proper escaping in plugin source code
    Locate the baf_sbox() function in the plugin files (typically in includes/ or shortcodes/ directory) and check if esc_attr() is applied to the vulnerable attributes before HTML output
    Affected if The function outputs sbox_id, sbox_class, placeholder, highlight_color, highlight_bg, or cont_ext_class without wrapping them in esc_attr()

You are affected if the plugin is installed, uses the baf_sbox shortcode with any of the vulnerable attributes (sbox_id, sbox_class, placeholder, highlight_color, highlight_bg, cont_ext_class), and those attributes are not properly escaped in the source code.

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

Update to a patched version of the plugin that applies proper esc_attr() escaping to all shortcode attributes before HTML interpolation. Until then, limit contributor-level access and review existing pages using the baf_sbox shortcode.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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