{"answers":{"affected":"2 open source packages ship an affected version, including admidio/admidio.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41659 exists.","fix":"Upgrade admidio/admidio to 5.0.9 or later.","what":"CVE-2026-41659 is a low-severity vulnerability in admidio, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41659 and fix it if it is affected.\n\nWhat it is: CVE-2026-41659 is a low-severity vulnerability in admidio, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41659 exists.\n\nAffected packages and fixed versions:\n- admidio/admidio (Packagist): affected all versions; fixed in 5.0.9\n- admidio/admidio (Packagist): affected all versions; fixed in 5.0.9\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41659/ (Markdown: https://insights.sbomify.com/CVE-2026-41659/index.md)","id":"CVE-2026-41659","markdown":"https://insights.sbomify.com/CVE-2026-41659/index.md","name":"CVE-2026-41659","record":{"aliases":["GHSA-68pr-7prh-mpv4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Admidio user management","requires_auth":"high_privilege","summary":"Role leaders can infer hidden user PII values via search results in Admidio, exposing sensitive data despite visibility settings.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Admidio is an open-source user management solution. Prior to version 5.0.9, the member assignment DataTables endpoint (members_assignment_data.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. This issue has been patched in version 5.0.9.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Admidio: Hidden Profile Field Values Leaked via Blind Search Oracle in Member Assignment","id":"CVE-2026-41659","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Admidio: Inverted 2FA Reset Authorization Check Lets Group Leaders Strip Admin TOTP","id":"CVE-2026-41660"},"packages":[{"ecosystem":"Packagist","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"admidio/admidio","purl":null,"source":"GHSA-68pr-7prh-mpv4"},{"ecosystem":"Packagist","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"admidio/admidio","purl":"pkg:composer/admidio/admidio","source":"GHSA-68pr-7prh-mpv4"}],"prev":{"headline":"Admidio: Missing Authorization on Inventory Module Destructive Endpoints Allows Any Authenticated User to Delete Items","id":"CVE-2026-41658"},"products":["admidio"],"published":"2026-05-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-07","vendors":["Admidio"]},"summary":"Role leaders can infer hidden user PII values via search results in Admidio, exposing sensitive data despite visibility settings.","url":"https://insights.sbomify.com/CVE-2026-41659/"}