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

CVE-2026-11783

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-27
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 8 weeks old

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 Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Product SKU in all versions up to, and including, 5.0.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with custom-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The malicious payload is delivered to site visitors — including unauthenticated users — when the store search widget inserts the unescaped AJAX response HTML into the DOM via jQuery's .html() method.

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 Dokan plugin fails to properly sanitize and escape the Product SKU field, allowing authenticated attackers with custom-level access to inject malicious JavaScript. This stored XSS persists in the database and executes when site visitors access pages displaying the SKU via the store search widget's AJAX response handler using jQuery's .html() method.

MitigationImplement proper input sanitization for SKU on save and output escaping (or use .text() instead of .html()) when displaying SKU data in the search widget response.

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. Identify if Dokan plugin is installed
    Locate the Dokan plugin folder in your WordPress wp-content/plugins directory or check via WordPress admin dashboard under Plugins. Note the installed version number.
    Affected if The Dokan plugin is present in the WordPress installation.
  2. Verify the installed Dokan version
    Check the main plugin file (usually dokan.php) for the version comment or use WordPress plugin administration to view version details. Compare this against any known affected version range if documented.
    Affected if The installed version falls within an affected range, if such a range exists.
  3. Inspect Product SKU fields in the database
    Query the WordPress postmeta table (typically wp_postmeta) where meta_key equals '_sku'. Look for meta_value entries containing script tags, iframe tags, or JavaScript event handlers (onload, onerror, onclick, etc.).
    Affected if Any Product SKU field contains raw HTML or JavaScript code, indicating unsanitized input was stored.
  4. Check if store search widget is active
    Verify if the Dokan store search widget is enabled in Appearance > Widgets or via theme customization. Identify if the AJAX response handler for search results is in use.
    Affected if The store search widget is active and returns SKU data via AJAX responses.
  5. Examine how SKU is rendered in search responses
    If access to theme or plugin source code is available, locate the AJAX handler for the store search widget. Verify whether .html() is used to display SKU data instead of .text() or proper escaping.
    Affected if The code uses .html() to output SKU values without sanitization, making the XSS triggerable.

You are affected if the Dokan plugin is installed, any Product SKU fields contain unsanitized script/HTML content, and the store search widget uses .html() to render SKU data in AJAX responses.

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 sanitization for SKU on save and output escaping (or use .text() instead of .html()) when displaying SKU data in the search widget response.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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