CVE-2026-131748 in BuddyPress Docs Plugininfo

Summary

by MITRE • 11/22/2026

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Boone Gorges BuddyPress Docs buddypress-docs allows Stored XSS.This issue affects BuddyPress Docs: from n/a through 2.2.7.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/22/2026

The identified vulnerability represents a classic instance of Improper Neutralization of Input During Web Page Generation, commonly known as Cross-Site Scripting or XSS. Specifically, this is classified under the Common Weakness Enumeration (CWE-79) and falls within the MITRE ATT&CK framework's Tactic TA0001 Initial Access via Technique T1189 Drive-by Client-Side Execution when exploited in a browser context, though its stored nature makes it more persistent. The flaw resides within the BuddyPress Docs plugin for WordPress, developed by Boone Gorges, and affects all versions from n/a through 2.2.7. This vulnerability allows an attacker to inject malicious client-side scripts into web pages viewed by other users, leveraging the trust that browsers have in content originating from a specific domain.

The technical root cause of this Stored XSS lies in the insufficient sanitization or validation of user-supplied input before it is rendered within the application's dynamic HTML output. In the context of BuddyPress Docs, which facilitates document sharing and management within WordPress communities, users can upload files, add descriptions, titles, or metadata associated with these documents. The vulnerability suggests that at least one entry point where this data is processed does not properly escape special characters such as angle brackets, quotes, ampersands, or other syntactically significant symbols used in HTML and JavaScript. When the application subsequently retrieves this unsanitized data to display it on a page, the browser interprets the injected script code as executable content rather than plain text. Because this is a stored vulnerability, the malicious payload is saved within the backend database of the WordPress site, ensuring that every time an authorized user or administrator views the affected document details, the script executes automatically in their session context.

The operational impact of this Stored XSS vulnerability is severe due to its persistence and potential for widespread exploitation. Unlike reflected XSS which requires tricking a specific victim into clicking a malicious link, stored XSS remains active on the server until manually removed by an administrator or patched via an update. This allows attackers to achieve persistent access to user sessions. By executing arbitrary JavaScript in the context of the vulnerable domain, an attacker can steal session cookies, authentication tokens, and other sensitive credentials that are not marked with secure flags such as HttpOnly or Secure. These stolen artifacts enable account takeover attacks against users who have administrative privileges within the BuddyPress environment. Furthermore, attackers can manipulate the DOM to deface websites, redirect users to phishing sites designed to harvest additional credentials, or perform actions on behalf of the victim without their knowledge, effectively bypassing same-origin policy protections that normally restrict cross-site interactions.

Mitigation strategies must address both immediate remediation and long-term security hygiene. The primary and most effective mitigation is to upgrade BuddyPress Docs to a version newer than 2.2.7 where this vulnerability has been patched by the developer through proper input validation and output encoding techniques. For organizations unable to immediately update, implementing Web Application Firewall rules can help detect and block common XSS payloads in HTTP requests targeting the affected endpoints. Additionally, administrators should enforce strict Content Security Policy headers that restrict script execution sources, although this is a compensating control rather than a fix for the underlying code flaw. From a development perspective, adhering to OWASP guidelines requires ensuring that all user inputs are contextually encoded before being inserted into HTML, JavaScript, CSS, or URL contexts. This includes using built-in escaping functions provided by frameworks and avoiding direct concatenation of untrusted data into DOM elements. Regular security audits and static code analysis tools should be employed during the software development lifecycle to identify such input handling flaws early, preventing them from reaching production environments where they pose significant risks to user privacy and system integrity.

Responsible

Patchstack

Reservation

11/17/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!