CVE-2023-48028VulnerabilityPublished 17 Nov 2023Updated 29 Sep 2025

CVE-2023-48028: n/a

Source CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 06:26 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

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

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Nov 2023
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-26.

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

AI-suggested

To mitigate this vulnerability, organizations should first verify if they are running kodbox version 1.46.01 and plan to upgrade to a patched version once available. In the absence of an official patch, administrators should implement the following measures: 1) Standardize login response messages to avoid revealing whether a username is valid or invalid, ensuring uniform error messages for all failed login attempts. 2) Implement account lockout policies or rate limiting to restrict the number of login attempts from a single IP address or account, thereby reducing the feasibility of brute force attacks. 3) Enable multi-factor authentication (MFA) on kodbox accounts to add an additional layer of security beyond passwords. 4) Monitor login attempts and authentication logs for unusual patterns indicative of enumeration or brute force activity. 5) Restrict access to the kodbox login page via IP whitelisting or VPN access where possible, limiting exposure to external attackers. 6) Conduct regular security assessments and penetration testing to identify and remediate similar issues proactively. These steps will help reduce the risk until an official patch is released.

Description

kodbox 1.46.01 has a security flaw that enables user enumeration. This problem is present on the login page, where an attacker can identify valid users based on varying response messages, potentially paving the way for a brute force attack.

Impact

For European organizations using kodbox 1.46.01, this vulnerability poses a significant risk to the confidentiality and integrity of their file management systems. Successful user enumeration can lead to targeted brute force attacks, potentially resulting in unauthorized access to sensitive files and data. This could compromise personal data protected under GDPR, intellectual property, or other confidential information. Additionally, unauthorized access could allow attackers to modify or delete files, impacting data integrity and availability. Organizations in sectors with high regulatory requirements or handling sensitive data, such as finance, healthcare, and government, are particularly at risk. The vulnerability could also serve as an entry point for further lateral movement within networks, escalating the impact beyond the initial compromise. Although exploitation requires interaction with the login interface, the ease of automating username enumeration and brute force attempts increases the threat level. Without a patch, organizations must rely on compensating controls to mitigate risk.

References

Community reviews

Loading reviews…