WordPress Plugin Buddypress 6.2.0 contains a persistent cross-site scripting vulnerability that allows authenticated attackers with moderator privileges to inject malicious script code through the figure parameter in wp:html blocks. Attackers can inject iframe elements with event handlers like onload that execute when administrators or privileged users preview or view the affected page content, enabling session hijacking and persistent phishing attacks.
Security readout for executives and security teams
Plain-English summary
BuddyPress 6.2.0 for WordPress has a stored cross-site scripting flaw. A moderator-level user could save malicious page content that runs in another privileged user's browser. The main business risk is compromise of admin sessions, deceptive content, or unauthorized site changes after a trusted account views the content.
Executive priority
Prioritize remediation for public or business-critical WordPress communities with multiple moderators. The vulnerability requires moderator privileges, but stored execution against administrators can turn a lower-privileged account into a broader site compromise path.
Technical view
CVE-2020-37233 is CWE-79 persistent XSS in BuddyPress 6.2.0. The source bundle says authenticated attackers with moderator privileges can inject script-capable markup through the figure parameter in wp:html blocks, which executes when administrators or privileged users preview or view affected content. CVSS 3.1 score is 6.4.
Likely exposure
Exposure appears limited to WordPress sites running BuddyPress 6.2.0 where moderator-level users can create or edit affected block content. Sites without BuddyPress, without version 6.2.0, or without untrusted moderator access are less likely exposed based on the provided sources.
Exploitation context
The bundle includes an Exploit-DB reference, so public exploit information exists. It does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a credible stored-XSS risk, especially where moderator accounts are numerous, shared, compromised, or externally managed.
Researcher notes
Evidence is sufficient for affected version, vulnerability class, privilege requirement, and impact direction. The source bundle does not provide a fixed version, vendor patch note, or active exploitation evidence. Avoid assuming affected versions beyond BuddyPress 6.2.0.
Mitigation direction
Check official BuddyPress guidance for a fixed or supported version before changing production systems.
Upgrade BuddyPress away from 6.2.0 when vendor guidance identifies a safe target release.
Restrict moderator privileges to trusted accounts until exposure is resolved.
Review moderator-created pages and posts for suspicious embedded active content.
Monitor administrator sessions and account activity for unexpected changes.
Validation and detection
Inventory WordPress sites and confirm whether BuddyPress 6.2.0 is installed.
Identify users with moderator-level permissions on affected sites.
Review pages using wp:html blocks for suspicious iframe or event-handler attributes.
Check recent administrator activity after viewing or previewing moderator-created content.
Confirm whether vendor advisories or release notes identify remediation for this CVE.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.