CVE-2023-51926VulnerabilityPublished 20 Jan 2024Updated 30 May 2025

CVE-2023-51926: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =23.05	Fixed in–

AI-suggested

European organizations should take immediate steps to mitigate CVE-2023-51926 by first identifying all instances of YonBIP version 3_23.05 within their environments. Since no official patches or vendor advisories are currently available, organizations should consider the following practical measures: 1) Implement strict network segmentation and access controls to limit exposure of YonBIP servers to untrusted networks; 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the CommonServletDispatcher component; 3) Conduct thorough code reviews and input validation enhancements around the affected servlet dispatcher to prevent arbitrary file path traversal or injection; 4) Monitor logs for anomalous access patterns indicative of file read attempts; 5) Restrict file system permissions of the application process to minimize accessible files; 6) Prepare for rapid patch deployment once vendor fixes become available by establishing communication channels with YonBIP maintainers or community; 7) Educate security teams on the vulnerability details to enable swift incident response. Additionally, organizations should review their data classification and encryption practices to reduce the impact of potential data exposure.

Description

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

Impact

For European organizations, the arbitrary file read vulnerability in YonBIP 3_23.05 could lead to significant confidentiality breaches, especially if the affected systems store sensitive personal data, intellectual property, or critical business information. Given the strict data protection regulations in Europe, such as GDPR, unauthorized disclosure of personal data could result in regulatory penalties and reputational damage. Organizations in sectors like finance, healthcare, government, and critical infrastructure that rely on YonBIP or similar Java-based middleware platforms are particularly at risk. Attackers exploiting this vulnerability could gain access to configuration files containing database credentials, API keys, or other secrets, enabling further lateral movement or escalation within the network. Although no integrity or availability impact is directly associated, the confidentiality breach alone can have cascading effects, including compliance violations and loss of customer trust. The absence of known exploits in the wild provides a window for proactive defense, but the ease of exploitation (no authentication or user interaction required) means attackers could quickly weaponize this vulnerability once details become public.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 16:28 UTC

Technical details

References

Community reviews

Related threats