Security readout for executives and security teams
Plain-English summary
This CVE describes a reported CORS issue in Connectwise Control 22.8.10013.8329. The vendor disputes the finding, saying wildcard CORS on two endpoints is intentional and not risky. Treat it as a validation item, not an emergency, unless your own testing shows sensitive cross-origin exposure.
Executive priority
Low priority for emergency response. Assign normal vulnerability-management review, especially where Connectwise Control is internet-facing or used for privileged remote administration. Escalate only if internal validation shows sensitive cross-origin data exposure.
Technical view
The report maps to CWE-942 and describes Access-Control-Allow-Origin wildcarding on two endpoints. CVSS 3.1 score is 6.1, requiring user interaction with low confidentiality and integrity impact. The CVE record states the vendor considers the report invalid because the behavior supports product functionality.
Likely exposure
Exposure is most relevant to environments running Connectwise Control 22.8.10013.8329. The CVE affected-product metadata is listed as n/a, so automated CPE matching may be unreliable. Confirm exposure through asset inventory and product version checks.
Exploitation context
The source bundle does not show active exploitation, and the CVE is not listed as KEV. The public record includes a GitHub report, but the vendor position in the CVE says the issue is not a valid vulnerability.
Researcher notes
Evidence is mixed: the CVE assigns medium CVSS and CWE-942, but the description records a vendor dispute and no accepted fix. Avoid assuming exploitability from wildcard CORS alone; validate whether credentials, sensitive responses, and browser enforcement create real impact.
Mitigation direction
- Check current vendor guidance for Connectwise Control CORS behavior.
- Inventory any Connectwise Control 22.8.10013.8329 instances.
- Keep Connectwise Control on vendor-supported versions.
- Review compensating controls around administrator sessions and trusted origins.
Validation and detection
- Confirm whether the named product version exists in your environment.
- Review endpoint CORS headers without attempting offensive exploitation.
- Check whether wildcard responses expose sensitive authenticated data.
- Document any finding against vendor guidance and business impact.
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-942: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-23128 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/l00neyhacker/CVE-2023-23128CVE 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.
Permissive Cross-domain Security Policy with Untrusted Domains
Permissive Cross-domain Security Policy with Untrusted Domains represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.