VulnerabilityPublished 16 Jan 2024Updated 2 Jun 2025

CVE-2023-39691

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

9.8Critical

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% 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:H/A:H

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 <=1.43	Fixed in–

AI-suggested

Given the critical severity and ease of exploitation, European organizations should immediately audit their environments to identify any deployments of kodbox, particularly versions up to 1.43. If kodbox is in use, organizations should seek vendor advisories or community patches addressing CVE-2023-39691 and apply them without delay. In the absence of official patches, organizations should consider temporarily disabling external access to kodbox instances or restricting access via network-level controls such as firewalls or VPNs to trusted users only. Implementing web application firewalls (WAFs) with custom rules to detect and block suspicious GET requests targeting administrator account creation endpoints can provide interim protection. Monitoring web server logs for unusual GET requests or sudden creation of new administrator accounts is critical for early detection. Organizations should also review and harden authentication and authorization configurations, and ensure that administrative access is logged and alerts are configured for anomalous activities. Finally, organizations should prepare incident response plans specific to web application compromises to rapidly contain and remediate any exploitation.

Description

An issue discovered in kodbox through 1.43 allows attackers to arbitrarily add Administrator accounts via crafted GET request.

Impact

For European organizations, the impact of this vulnerability could be severe, especially for those using kodbox as part of their web infrastructure or file management solutions. Unauthorized administrative access could lead to data breaches involving sensitive personal data protected under GDPR, resulting in legal and financial penalties. The integrity of critical business data and operational continuity could be compromised, leading to reputational damage and potential operational downtime. Organizations in sectors such as government, finance, healthcare, and critical infrastructure, where file management systems are integral, could face heightened risks. Additionally, the ease of exploitation and lack of authentication requirements mean that attackers could rapidly compromise vulnerable systems, potentially using them as footholds for further lateral movement within networks or for launching ransomware attacks. The absence of known exploits in the wild currently provides a limited window for proactive mitigation before widespread exploitation occurs.

References

blog.mo60.cn/index.php/archives/kodbox_Logical.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 16:26 UTC

Technical details

References

Community reviews

Related threats