Security readout for executives and security teams
Plain-English summary
Bagecms v3.1.0 has a stored XSS flaw in the Custom Settings module. An attacker who can place crafted content there may cause malicious script or HTML to run when another user views the stored content. Business urgency depends on whether Bagecms is deployed and who can modify Custom Settings.
Executive priority
Prioritize if Bagecms v3.1.0 is internet-facing or used by staff with sensitive sessions. If not deployed, document non-exposure. If deployed, reduce write access and seek vendor remediation promptly.
Technical view
CVE-2023-37122 describes stored cross-site scripting in Bagecms v3.1.0 via crafted input injected into the Custom Settings module. The public bundle does not include CVSS, CWE mapping, authentication requirements, affected CPEs, or a named patched version.
Likely exposure
Exposure is likely limited to environments running Bagecms v3.1.0, especially where the Custom Settings module is reachable by untrusted or lower-privileged users. The provided affected-product metadata is incomplete.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. A public GitHub issue exists, so defenders should treat technical details as publicly discoverable.
Researcher notes
The source bundle is sparse: severity is unknown, CVSS is absent, CWE is absent, authentication context is not stated, and no fixed version is named. Avoid assuming broader Bagecms versions are affected without vendor confirmation.
Mitigation direction
- Identify any Bagecms v3.1.0 deployments.
- Check vendor or project guidance for fixed releases.
- Restrict Custom Settings access to trusted administrators.
- Review Custom Settings content for unexpected scripts or HTML.
- Apply output encoding and input validation where maintainable.
Validation and detection
- Confirm deployed Bagecms versions against v3.1.0.
- Review who can modify the Custom Settings module.
- Inspect stored Custom Settings values for suspicious HTML or script content.
- Safely test rendering behavior in a controlled environment.
- Monitor the linked GitHub issue and CVE record for updates.
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-2023-37122 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/bagesoft/bagecms/issues/6CVE 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.