CVE-2024-28061VulnerabilityPublished 28 May 2024Updated 30 May 2025

CVE-2024-28061: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.3Medium

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

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

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

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 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-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

Affected software

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

AI-suggested

Organizations should first identify if Apiris Kafeo 6.4.4 is deployed within their environment and assess the exposure of the embedded database files. Until an official patch or vendor guidance is available, the following mitigations are recommended: 1) Restrict network access to systems running Apiris Kafeo to trusted internal networks and limit user privileges to the minimum necessary to reduce the risk of privilege misuse. 2) Implement strict access controls and monitoring on the embedded database files, including file system permissions and encryption at rest where possible. 3) Conduct regular audits and integrity checks of the database contents to detect unauthorized access or modifications. 4) Employ network segmentation and intrusion detection systems to identify suspicious activities targeting the application or its database. 5) Prepare incident response plans specific to data breaches involving embedded databases. 6) Monitor vendor communications for patches or updates addressing this vulnerability and apply them promptly once available. 7) Consider compensating controls such as application-layer encryption of sensitive data before storage in the embedded database to reduce exposure.

Description

An issue was discovered in Apiris Kafeo 6.4.4. It permits a bypass, of the protection in place, to access to the data stored in the embedded database file.

Impact

For European organizations using Apiris Kafeo 6.4.4, this vulnerability poses a risk of unauthorized data exposure or modification within the embedded database. This could lead to leakage of sensitive business or personal data, potentially violating GDPR requirements for data protection and privacy. The integrity impact could allow attackers to alter stored data, undermining trust in the system's outputs or causing operational disruptions. Availability impact, while rated low, could still affect business continuity if critical data becomes inaccessible or corrupted. Given the network attack vector and low complexity, attackers with some level of privileges (e.g., internal users or compromised accounts) could exploit this vulnerability remotely without user interaction, increasing the risk in environments where network access is not tightly controlled. The absence of known exploits reduces immediate risk, but organizations should not be complacent given the potential for future exploitation. The impact is more pronounced in sectors handling sensitive or regulated data, such as finance, healthcare, and government services across Europe.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats