Summary
EGroupware has SQL Injection in Nextmatch Filter Processing
Impact
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
1. Input Validation (Whitelisting)
Do not rely solely on is_int() for security decisions when handling external input, especially JSON data where keys can be numeric strings. Implement a strict whitelist (allowlist) of allowed column names for filtering in Nextmatch widgets. If the key/column is not in the whitelist, reject the request.
2. Parameter Binding
Ensure all filter values are bound as parameters (prepared statements) rather than being concatenated directly into the SQL string.
3. Strict Type Checking
When processing JSON input, ensure that keys are strictly checked against expected types (e.g., using === for strict comparison or filter_var) before being used in SQL generation logic.
Frequently Asked Questions
- What is CVE-2026-22243? CVE-2026-22243 is a high-severity SQL injection vulnerability in egroupware/egroupware (composer), affecting versions < 23.1.20260113. It is fixed in 23.1.20260113, 26.0.20260113. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of egroupware/egroupware are affected by CVE-2026-22243? egroupware/egroupware (composer) versions < 23.1.20260113 is affected.
- Is there a fix for CVE-2026-22243? Yes. CVE-2026-22243 is fixed in 23.1.20260113, 26.0.20260113. Upgrade to this version or later.
- Is CVE-2026-22243 exploitable, and should I be worried? Whether CVE-2026-22243 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-22243 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-22243?
- Upgrade
egroupware/egroupwareto 23.1.20260113 or later - Upgrade
egroupware/egroupwareto 26.0.20260113 or later
- Upgrade