Subscriber-level stored XSS via unescaped display names
Published Jun 12, 2024 · Updated Apr 8, 2026
Stored XSS in the Members block in BuddyPress before 12.5.1 allows remote authenticated users to inject scripts through display names. The renderer in bp-members-blocks.php places a member's display_name value into generated member markup without sufficient sanitization and output escaping, leaving stored script content executable. Subscriber-level access is sufficient, and the payload runs in a visitor's browser when the affected Members block is viewed.
Summary
What happened
Stored XSS in the Members block in BuddyPress before 12.5.1 allows remote authenticated users to inject scripts through display names. The renderer in bp-members-blocks.php places a member's display_name value into generated member markup without sufficient sanitization and output escaping, leaving stored script content executable. Subscriber-level access is sufficient, and the payload runs in a visitor's browser when the affected Members block is viewed.
The record
- CVE
- CVE-2024-4892
- Published
- Jun 12, 2024
- Updated
- Apr 8, 2026
- Vendor
- BuddyPress
- Product
- BuddyPress
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=12.5.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo