Security readout for executives and security teams
Plain-English summary
CVE-2022-23350 is reported as a cross-site scripting vulnerability in BigAnt Software BigAnt Server v5.6.06. XSS can let an attacker make a victim’s browser run attacker-controlled script in the application context. The public record gives limited technical detail and no CVSS score.
Executive priority
Treat as a targeted validation item, not an emergency based on current evidence. Prioritize quickly if BigAnt Server v5.6.06 is internet-facing or used by privileged staff.
Technical view
The CVE description identifies XSS in BigAnt Server v5.6.06. The bundled affected-product metadata is incomplete, and no CWE, CVSS vector, vulnerable parameter, authentication requirement, or fixed version is provided. A public GitHub proof-of-concept reference is listed, but active exploitation is not supported by KEV or the supplied sources.
Likely exposure
Exposure is most likely limited to organizations running BigAnt Software BigAnt Server v5.6.06. Confirm directly, because the structured affected-product fields in the source bundle are marked n/a.
Exploitation context
CISA KEV status is false in the bundle, so active exploitation is not established. The CVE references a public PoC repository, which raises validation urgency but does not prove real-world exploitation.
Researcher notes
Evidence is thin: no CVSS, CWE, endpoint, parameter, auth context, or patch data is supplied. The public PoC reference should be reviewed carefully for reproducibility and scope, but do not infer broader affected versions without vendor or CVE evidence.
Mitigation direction
- Inventory BigAnt Server deployments and identify any v5.6.06 instances.
- Check BigAnt vendor guidance for fixed releases or official mitigations.
- Reduce exposure of affected web interfaces until vendor guidance is confirmed.
- Apply a vendor-supported update or workaround if one is available.
- Monitor application logs and user reports for suspicious browser-side behavior.
Validation and detection
- Confirm installed BigAnt Server versions across servers and images.
- Determine whether v5.6.06 interfaces are reachable by untrusted users.
- Review CVE and vendor references for updated affected-version or fix details.
- Assess exposure in a test environment without running offensive checks in production.
- Verify compensating controls limit access to affected web interfaces.
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-2022-23350 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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/bzyo/cve-pocs/tree/master/CVE-2022-23350CVE reference, mitre
- https://www.bigantsoft.com/CVE reference, mitre
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.