LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51926: YonBIP v3_23.05 was discovered to contain an arbitrary file read vulnerability via the nc.bs.framework.comn...

YonBIP v3_23.05 was discovered to contain an arbitrary file read vulnerability via the nc.bs.framework.comn.serv.CommonServletDispatcher component.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-51926 is a high-severity arbitrary file read issue reported in YonBIP v3_23.05. If reachable by attackers, it could expose sensitive files without authentication. The public record is sparse, so business urgency depends on whether your environment runs this specific YonBIP version and exposes the affected component.

Executive priority

Treat as high priority if YonBIP is deployed, because the reported impact is unauthenticated exposure of sensitive files. If YonBIP is not present, document non-exposure. Because patch details are not in the bundle, assign ownership to confirm vendor guidance quickly.

Technical view

The CVE describes an arbitrary file read vulnerability in nc.bs.framework.comn.serv.CommonServletDispatcher in YonBIP v3_23.05. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, indicating unauthenticated network access with high confidentiality impact and no stated integrity or availability impact.

Likely exposure

Potentially exposed organizations are those running YonBIP v3_23.05, especially if the affected servlet component is reachable over a network or the internet. The CVE metadata does not provide CPEs, vendor/product normalization, or a confirmed affected-version range beyond the description.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. A public GitHub reference is listed, but the provided bundle does not establish real-world exploitation, available patches, or vendor-confirmed remediation.

Researcher notes

Evidence is limited to CVE metadata and two references. No CWE, CPE, affected vendor field, patch version, or exploit-status confirmation is provided. Use the component name, YonBIP v3_23.05, and CVSS vector as the primary investigation anchors.

Mitigation direction

  • Check Yonyou guidance for fixed versions or supported workarounds.
  • Remove public exposure for affected YonBIP services where possible.
  • Restrict access to trusted networks and authenticated administrative paths.
  • Increase monitoring around YonBIP file access and servlet requests.
  • Prioritize upgrade or remediation once vendor guidance is confirmed.

Validation and detection

  • Inventory YonBIP deployments and confirm exact versions.
  • Check whether v3_23.05 exists in production or staging.
  • Confirm whether CommonServletDispatcher is present and network-reachable.
  • Review logs for suspicious file-read activity without replaying attacks.
  • Track CVE and vendor pages for remediation updates.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51926 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-51926Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.