CVE-2026-104760 · Other
NO FIX YET · SEE WHAT TO DO
The weDocs WordPress plugin does not sanitize the modalPlaceholder block attribute, so a contributor can save a script into a post. The script runs in the browser of any admin or editor who previews the pending post.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the weDocs plugin version 2.6.1 or earlier where contributors can write posts. Exposure depends on the contributor role being able to save pending posts with the weDocs block, and on admins or editors previewing those posts. Sites without the plugin or without contributor accounts are not affected.
Not affected if no-contributor-accounts, plugin-above-2.6.1, plugin-not-installed
Who cares self-hosted, wedocs, wordpress
2.6.1 and earlier are listed as affected.2.6.1 per the NVD entry; the exact fixed version is unknown.The weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'modalPlaceholder' Block Attribute in all versions up to, and including, 2.6.1 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. Because Contributors can save posts in pending status, a malicious payload in the modalPlaceholder block attribute will execute in the browser of any admin or editor who previews or views the pending post.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.