Security readout for executives and security teams
Plain-English summary
A WordPress plugin can let logged-in contributors store malicious scripts in team-builder shortcode content. Those scripts may run when someone views the affected page, creating account and content-integrity risk for sites using the plugin.
Executive priority
Treat this as a moderate-priority web content integrity issue. It is not reported as actively exploited, but it can affect visitors or administrators if a contributor account is misused. Prioritize sites with many authors or weak account controls.
Technical view
CVE-2024-13591 is stored XSS in Team Builder For WPBakery Page Builder through the team-builder-vc shortcode. Versions up to and including 1.0 lack sufficient sanitization and output escaping for user-supplied attributes. The CVSS 3.1 score is 6.4, with low privileges required and changed scope.
Likely exposure
Exposure is limited to WordPress sites running Team Builder For WPBakery Page Builder version 1.0 or earlier. Risk is higher where contributor-level accounts are widely granted or may be compromised. The source bundle does not identify CPEs or a fixed version.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked in KEV. Abuse requires authenticated contributor-level access or higher. Successful injection can execute scripts for users who access affected pages.
Researcher notes
Evidence supports authenticated stored XSS in shortcode attributes due to missing sanitization and escaping. Public references include the WordPress plugin source locations and Wordfence advisory. No exploit status, patch version, or vendor remediation detail is provided in the bundle.
Mitigation direction
- Inventory WordPress sites for this plugin and version 1.0 or earlier.
- Check Wordfence, WordPress plugin repository, and vendor guidance for a fixed release or official mitigation.
- Disable or remove the plugin where business impact permits until remediation is confirmed.
- Restrict contributor-level access to trusted accounts only.
- Review affected pages for unexpected shortcode attributes or script behavior.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record installed plugin versions and compare against up to and including 1.0.
- Review contributor and higher WordPress accounts for unnecessary access.
- Inspect pages using the team-builder-vc shortcode for suspicious stored content.
- Verify remediation guidance from the vendor or Wordfence before closing the finding.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2024-13591 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e6b1e4d9-03dc-47e8-ab41-ae9c04dc0132?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/team-builder-for-wpbakery-page-builder/tags/1.0/includes/style10.php#L2CVE reference
- https://plugins.trac.wordpress.org/browser/team-builder-for-wpbakery-page-builder/tags/1.0/plugin.class.php#L55CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.