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

CVE-2026-12731

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-03
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 7 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 weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'sectionTitleTag' and 'articleTitleTag' Block Attributes 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 confidence

The weDocs WordPress plugin versions up to 2.3.0 fail to properly sanitize and escape the 'sectionTitleTag' and 'articleTitleTag' block attribute values, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript that persists on affected pages and executes when visited.

MitigationUpdate the weDocs plugin to version 2.3.1 or later, which should include proper input sanitization using functions like sanitize_html_class or esc_attr and output escaping with esc_html or esc_url.

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. Check if weDocs plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for weDocs, or check the /wp-content/plugins/wedocs/ directory exists and contains plugin files
    Affected if weDocs plugin is not installed or the directory does not exist
  2. Determine installed weDocs version
    In WordPress admin plugins list, check the version number displayed under weDocs, or open the main plugin file (usually wedocs.php) and locate the Version header in the plugin comment block
    Affected if Version is 2.3.0 or earlier (any version up to and including 2.3.0)
  3. Identify pages using weDocs blocks
    Search the WordPress database (wp_posts table) for posts containing the weDocs block markup, or use WP-CLI: wp post list --post_type=any --format=ids | xargs -I {} wp post get {} --format=json | jq -r '.content.raw' | grep -l wedocs
    Affected if weDocs blocks are present in any published content
  4. Inspect block attributes for vulnerable values
    Examine the block content in the database or block editor for 'sectionTitleTag' or 'articleTitleTag' attributes. In the database, search wp_posts for patterns like 'sectionTitleTag' or 'articleTitleTag' within block JSON
    Affected if Any weDocs block contains sectionTitleTag or articleTitleTag attributes with unescaped HTML or JavaScript (e.g., onmouseover, onclick tags)

You are affected if weDocs plugin version 2.3.0 or earlier is installed AND any page uses weDocs blocks with sectionTitleTag or articleTitleTag attributes containing malicious script.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the weDocs plugin to version 2.3.1 or later, which should include proper input sanitization using functions like sanitize_html_class or esc_attr and output escaping with esc_html or esc_url.

Recommended fix Moderate confidence

Latest version greater than 2.3.0 (check wordpress.org for the current stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running a version newer than 2.3.0
  6. 6. Test the plugin's block editor functionality to confirm the XSS fix is working correctly
  7. 7. If automatic updates are not enabled, consider enabling them for this plugin or manually download the latest version from wordpress.org/plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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