Security readout for executives and security teams
Plain-English summary
OpenWebif through 1.4.7 can store attacker-supplied JavaScript in the Bouquet Editor’s Add Bouquet feature. If a user later views the affected page, that script may run in their browser. The sources do not provide CVSS scoring, confirmed exploitation, or a named fixed release.
Executive priority
Treat this as a targeted management-interface web risk, not a confirmed internet-wide emergency. Prioritize systems exposing OpenWebif beyond trusted administrators, then confirm vendor remediation status.
Technical view
CVE-2021-38113 describes Stored XSS in addBouquet in js/bqe.js, reached via bouqueteditor/api/addbouquet?name=. The affected component is OpenWebif, also known as e2openplugin-OpenWebif, through 1.4.7. The public record does not list CWE, CVSS, CPEs, or remediation details.
Likely exposure
Exposure is likely limited to OpenWebif deployments through version 1.4.7 where the Bouquet Editor and add-bouquet API are accessible to users or networks that should not be trusted.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Stored XSS can still matter when management interfaces are reachable by lower-trust users, shared accounts, or exposed administrative networks.
Researcher notes
Evidence is sparse: the CVE record identifies the vulnerable function, endpoint parameter, product name, and version boundary, but omits CVSS, CWE, CPEs, exploit status, and patch details. Avoid assuming broader product impact without vendor confirmation.
Mitigation direction
- Check vendor issue and release guidance for any fixed OpenWebif version.
- Restrict OpenWebif access to trusted administrative networks only.
- Require authentication and least-privilege access for Bouquet Editor functions.
- Review whether OpenWebif through 1.4.7 remains deployed.
- Monitor vendor advisories before treating any workaround as complete.
Validation and detection
- Inventory OpenWebif instances and record exact installed versions.
- Confirm whether Bouquet Editor is enabled and reachable.
- Review access controls for bouqueteditor/api/addbouquet.
- Inspect logs for unusual addbouquet name values or unexpected editor activity.
- Verify bouquet names are safely encoded when displayed.
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.
CVE-2021-38113 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/E2OpenPlugins/e2openplugin-OpenWebif/issues/1387CVE reference · x_refsource_MISC
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.