WPIntell

Source evidence

Security Vulnerability Notice for BetterDocs – Request for Cl

BetterDocs – AI Documentation, Knowledge Base, Docs, Wikis, FAQ with Chatbot · support · 2026-06-19T09:05:00+00:00

mixedsentiment
highseverity
0.95relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 26 rows with source links

11.5% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

23 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
michaelbarnettii resolved
Hello BetterDocs Team, We recently received a security notification from the Wordfence plugin on our website indicating that the BetterDocs plugin may contain a security vulnerability. The scan reported the following: Plugin: BetterDocs Severity: 6.4/10.0 (Medium) Reported by: Wordfence Scan Date: June 19, 2026 Could you please provide clarification regarding this reported vulnerability? Specifically, we would appreciate information on: Whether this is a known vulnerability affecting BetterDocs. Which versions are impacted. Whether the issue has already been patched in a recent release. Any recommended mitigation steps if a fix is not yet available. Any official security advisory or CVE reference related to this report. We are currently using BetterDocs on our production website and would like to ensure that our installation remains secure. Thank you for your assistance. We look forward to your clarification and any further updates. Hi @michaelbarnettii Greetings! I think the check was run against an older version of BetterDocs.Yes, this was a known issue and we already addressed it. 🙂 An authenticated (contributor) stored XSS via the blockId block attribute, affecting version 4.5.3 and earlier. The good news is that it’s already been fixed. Our dev team ran a fresh vulnerability scan against our latest release (4.5.4) and confirmed the issue is fully resolved. 🙂 Our recommendation is simply to update BetterDocs to version 4.5.4 and you’ll be all set. So, Kindly update BetterDocs to 4.5.4 and re-scan, let us know the status. Let us know if you have any other questions — happy to help! Best regards Hi @michaelbarnettii Greetings! We have not heard from you since our last reply. Could you please share the status after updating of BetterDocs version, 4.5.4 . Looking forward to hearing from you. 🙂 Thanks Hello @michaelbarnettii , Hope you’re doing well. As we’re not getting any response from you, we are assuming your issue has been solved. And so, we’re going to mark this topic as resolved now. If the issue still persists, feel free to reply here and we’ll be happy to assist further. Thank you.

Comments

3 shown
Amin 2026-06-19T11:37:00+00:00

Hi @michaelbarnettii Greetings! I think the check was run against an older version of BetterDocs.Yes, this was a known issue and we already addressed it. 🙂 An authenticated (contributor) stored XSS via the blockId block attribute, affecting version 4.5.3 and earlier. The good news is that it’s already been fixed. Our dev team ran a fresh vulnerability scan against our latest release (4.5.4) and confirmed the issue is fully resolved. 🙂 Our recommendation is simply to update BetterDocs to version 4.5.4 and you’ll be all set. So, Kindly update BetterDocs to 4.5.4 and re-scan, let us know the status. Let us know if you have any other questions — happy to help! Best regards

Amin 2026-06-22T08:44:00+00:00

Hi @michaelbarnettii Greetings! We have not heard from you since our last reply. Could you please share the status after updating of BetterDocs version, 4.5.4 . Looking forward to hearing from you. 🙂 Thanks

Sadman Sakib Nadvi 2026-06-25T11:33:00+00:00

Hello @michaelbarnettii , Hope you’re doing well. As we’re not getting any response from you, we are assuming your issue has been solved. And so, we’re going to mark this topic as resolved now. If the issue still persists, feel free to reply here and we’ll be happy to assist further. Thank you.