VulnerabilityPublished 7 Jul 2024Updated 25 Nov 2025

CVE-2024-40614: egroupware · CVE-2024-40614 is a medium-severity SQL injection

Affects egroupwareSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 23.1.20240624 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 23.1.20240624

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: 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: 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 7 Jul 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

Upgrade egroupware/egroupware to 23.1.20240624.

Affected software

Product	Affected	Fixed in
GitHubegroupware/egroupware`pkg:github/egroupware/egroupware`Other threats	Affected <23.1.20240624	Fixed in 23.1.20240624

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should monitor for the official release of EGroupware version 23.1.20240624 or later that addresses this vulnerability and apply updates promptly. If you cannot patch yet, restrict access to the Address Book and InfoLog modules to trusted users only and enforce strong authentication and session management controls. Implement web application firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the sort.id parameter. Conduct regular audits of user privileges to minimize the number of users with access to vulnerable functionality. Additionally, review and harden database permissions to limit the impact of potential SQL injection. Employ monitoring and alerting for unusual database queries or access patterns. Educate users about the risks of credential compromise to reduce insider threat vectors.

Description

CVE-2024-40614 is a medium-severity SQL injection vulnerability in EGroupware versions before 23.1.20240624. It arises from improper handling of the ORDER BY clause in the ajax_get_rows function used for sorting Address Book or InfoLog entries. Authenticated users can exploit this flaw to inject SQL code via the sort.id parameter, potentially exposing sensitive data. The vulnerability does not require user interaction but does require authentication with low privileges. There are no known exploits in the wild yet, and no official patches have been linked at the time of publication. European organizations using vulnerable EGroupware versions for collaboration and contact management are at risk. Mitigation involves promptly updating to the fixed version once available and restricting access to the affected modules.

Impact

For European organizations, the impact centers on potential unauthorized access to sensitive contact and project information managed within EGroupware. This could lead to data breaches involving personal data, internal communications, or business-critical information, raising compliance concerns under GDPR and other data protection regulations. The requirement for authentication limits exploitation to insiders or compromised accounts, but the low privilege needed increases risk from regular users or attackers who gain basic access. The exposure of confidential data can damage organizational reputation, lead to financial penalties, and facilitate further attacks. Organizations relying heavily on EGroupware for collaboration, especially in sectors like government, healthcare, and finance, face heightened risks. The absence of known exploits reduces immediate threat but underscores the need for proactive remediation.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Dec 2025, 14:51 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats