EGroupware Vulnerable to Local File Inclusion via file:// URI in Mail Compose
CVE-2026-45016GHSA-c8m7-r2jv-rw63
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (egroupware/egroupware 26.5.20260507, 23.1.20260601), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist egroupware/egroupware
- Affected
- >= 26.0.20251208, < 26.5.20260507< 23.1.20260601
- Fixed in
- 26.5.20260507, 23.1.20260601
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-c8m7-r2jv-rw63 lists affected ranges: Packagist egroupware/egroupware >=26.0.20251208 =0 <23.1.20260601
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary The function processes image URLs embedded in an HTML email body without validating or restricting URI schemes. The check !strstartswith($myUrl, 'http') evaluates to true for file:// URIs, causing filegetcontents($basedir . urldecode($myUrl)) to read arbitrary files from the server filesystem and embed them as inline MIME attachments in outgoing email. strstartswith('file:///etc/passwd', 'http') → false !false → true PoC 1. Log in as any authenticated EGroupware user with mail access and open the mail compose window. 2. Switch to HTML body mode and insert: <img src="file:///etc/passwd". 3. The server executes filegetcontents('file:///etc/passwd'), writes the content to a temp file, and attaches it as an inline MIME part. Impact An authenticated attacker can read arbitrary files accessible by the web server process, including /etc/passwd, application configuration files containing database credentials, private TLS keys, and environment files. Remediation Enforce a strict URI…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-c8m7-r2jv-rw63
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-45016 Advisory: EGroupware Vulnerable to Local File Inclusion via file:// URI in Mail Compose IDs: CVE-2026-45016, GHSA-c8m7-r2jv-rw63 Record: https://patchnext.com/advisories/cve-2026-45016 (revision 1, source checked 26 Oct 2026, 14:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: egroupware/egroupware 26.5.20260507, 23.1.20260601. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist egroupware/egroupware: affected >= 26.0.20251208, < 26.5.20260507; < 23.1.20260601; fixed in 26.5.20260507, 23.1.20260601 ## Suggested inspection (read-only) - Packagist egroupware/egroupware: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on egroupware/egroupware. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-c8m7-r2jv-rw63 (GitHub-reviewed advisory GHSA-c8m7-r2jv-rw63 lists affected ranges: Packagist egroupware/egroupware >=26.0.20251208 =0 <23.1.20260601) Commands are suggestions: review each one before running it.
Loading voting…