Security readout for executives and security teams
Plain-English summary
CVE-2023-6938 is a stored cross-site scripting issue in the Oxygen Builder WordPress plugin through version 4.8. A contributor-level user could store script content in a custom field that later runs for visitors to the affected page.
Executive priority
Treat this as a moderate WordPress application risk. Prioritize sites with many content contributors or weaker account controls, because successful abuse can affect users who view compromised pages.
Technical view
The vulnerability is CWE-79 caused by insufficient input sanitization and output escaping for custom-field dynamic data in Oxygen Builder <=4.8. It requires authenticated contributor-or-higher access, is network reachable, low complexity, and has CVSS 3.1 score 6.4.
Likely exposure
Exposure is most likely on WordPress sites running Oxygen Builder 4.8 or earlier, especially where contributor accounts are available to contractors, authors, customers, or compromised users.
Exploitation context
The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. Practical risk depends on whether an attacker can obtain contributor-level access and whether privileged users view injected pages.
Researcher notes
Evidence supports an authenticated stored XSS via custom fields in Oxygen Builder <=4.8, addressed in 4.8.1 through optional output escaping for dynamic data. Sources do not provide exploit telemetry, proof-of-concept details, or broader product impact.
Mitigation direction
- Upgrade Oxygen Builder beyond version 4.8, starting with 4.8.1 or later.
- Review Oxygen guidance on filtering dynamic data output.
- Limit contributor-level access to trusted users only.
- Audit existing custom fields and pages for unexpected script content.
Validation and detection
- Inventory WordPress sites using Oxygen Builder and record plugin versions.
- Confirm affected sites are not running Oxygen Builder 4.8 or earlier.
- Review user roles for unnecessary contributor-or-higher permissions.
- Check rendered pages using custom-field dynamic data for unsafe script execution risk.
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-2023-6938 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
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.
