Admidio Leaks Hidden Profile Field Values via Blind Search Oracle in Member Assignment
CVE-2026-41659GHSA-68pr-7prh-mpv4
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (admidio/admidio 5.0.9), 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 admidio/admidio
- Affected
- <= 5.0.8
- Fixed in
- 5.0.9
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-68pr-7prh-mpv4 lists affected ranges: Packagist admidio/admidio >=0 <=5.0.8
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
- 2.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-41659: 0.26% estimated exploitation activity in the next 30 days; percentile 17.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The member assignment DataTables endpoint (membersassignmentdata.php) includes hidden profile fields (BIRTHDAY, STREET, CITY, POSTCODE, COUNTRY) in its SQL search condition regardless of field visibility settings. While the JSON output correctly suppresses hidden columns via isVisible() checks, the server-side search operates at the SQL level before any visibility filtering. This allows a role leader with assign-only permissions to infer hidden PII values by observing which users appear in search results for specific values. Details The search columns are hardcoded at modules/groups-roles/membersassignmentdata.php:118-126: These columns are concatenated into a SQL LIKE search at line 139: The SQL query at lines 200-235 fetches all these fields via LEFT JOINs on admuserdata, and the search condition is applied as a subquery filter at lines 258-262: The output visibility checks at lines 291-335 correctly call $gProfileFields-isVisible('BIRTHDAY',…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-68pr-7prh-mpv4
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-41659 Advisory: Admidio Leaks Hidden Profile Field Values via Blind Search Oracle in Member Assignment IDs: CVE-2026-41659, GHSA-68pr-7prh-mpv4 Record: https://patchnext.com/advisories/cve-2026-41659 (revision 1, source checked 26 Oct 2026, 14:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 2.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: admidio/admidio 5.0.9. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist admidio/admidio: affected <= 5.0.8; fixed in 5.0.9 ## Suggested inspection (read-only) - Packagist admidio/admidio: 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 admidio/admidio. - 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-68pr-7prh-mpv4 (GitHub-reviewed advisory GHSA-68pr-7prh-mpv4 lists affected ranges: Packagist admidio/admidio >=0 <=5.0.8) Commands are suggestions: review each one before running it.
Loading voting…