CVE-2026-12734
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 · uneditedThe weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'connectorWidth' Block Attribute in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping. 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 confidenceThe weDocs WordPress plugin is vulnerable to stored XSS via the 'connectorWidth' block attribute in versions up to 2.3.0. Insufficient input sanitization allows authenticated contributors+ to inject arbitrary JavaScript that executes when other users access affected pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm weDocs plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'weDocs' in the list. Note whether it is active or inactive.Affected if weDocs plugin is installed and active
-
Identify installed weDocs versionClick 'View Details' on the weDocs plugin in the plugins list, or check the plugin header in /wp-content/plugins/wedocs/includes/wedocs.php for the 'Version' field. Compare this version number to 2.3.0.Affected if Installed version is 2.3.0 or lower (any version up to and including 2.3.0)
-
Check for contributor or higher user accountsIn WordPress admin, go to Users > All Users and review the 'Role' column. Count the number of accounts with 'Contributor', 'Author', 'Editor', or Administrator roles.Affected if There is at least one user with Contributor, Author, Editor, or Administrator role (these roles can create or edit content containing the vulnerable attribute)
-
Inspect for use of weDocs shortcode or block with connectorWidthSearch post/page content for the weDocs shortcode (such as [weDocs] or [docs]) or check if the weDocs Gutenberg block is in use. Review whether any documentation pages display a layout with connectors where the connectorWidth attribute could be present in the block settings.Affected if weDocs shortcode or block is used on any published page, and the connectorWidth attribute setting is accessible or has been configured
You are affected if weDocs plugin version 2.3.0 or lower is active and you have users with Contributor-level access or higher who can create or edit content using the weDocs block or shortcode.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the weDocs plugin to version 2.3.1 or later. If an update is unavailable, restrict contributor-level user permissions or temporarily disable the plugin until a patch is released.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12734 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12734 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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