{"answers":{"affected":"2 open source packages ship an affected version, including ibexa/core.","exploited":"There is no known exploitation of GHSA-394j-x37r-2q27 in the wild and no public exploit code.","fix":"Upgrade ibexa/core to 4.2.3 or later.","what":"GHSA-394j-x37r-2q27 is a vulnerability in ibexa/core, published on 10 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-394j-x37r-2q27 and fix it if it is affected.\n\nWhat it is: GHSA-394j-x37r-2q27 is a vulnerability in ibexa/core, published on 10 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-394j-x37r-2q27 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ibexa/core (Packagist): affected from 4.2.0; fixed in 4.2.3\n- ibexa/core (Packagist): affected from 4.2.0; fixed in 4.2.3\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/GHSA-394j-x37r-2q27/ (Markdown: https://insights.sbomify.com/GHSA-394j-x37r-2q27/index.md)","id":"GHSA-394j-x37r-2q27","markdown":"https://insights.sbomify.com/GHSA-394j-x37r-2q27/index.md","name":"GHSA-394j-x37r-2q27","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Ibexa DXP","requires_auth":"low_privilege","summary":"Users with Company admin or role assignment policies can bypass subtree limitations to assign any role to any user, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Critical severity. Users with the Company admin role (introduced by the company account feature in v4) can assign any role to any user. This also applies to any other user that has the role / assign policy. Any subtree limitation in place does not have any effect.\n\nThe role / assign policy is typically only given to administrators, which limits the scope in most cases, but please verify who has this policy in your installaton. The fix ensures that subtree limitations are working as intended.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Ibexa DXP users with the Company admin role can assign any role to any user","id":"GHSA-394j-x37r-2q27","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["4.2.3"],"introduced":["4.2.0"],"last_affected":[],"package":"ibexa/core","purl":null,"source":"GHSA-394j-x37r-2q27"},{"ecosystem":"Packagist","fixed":["4.2.3"],"introduced":["4.2.0"],"last_affected":[],"package":"ibexa/core","purl":"pkg:composer/ibexa/core","source":"GHSA-394j-x37r-2q27"}],"products":null,"published":"2022-11-10","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Users with Company admin or role assignment policies can bypass subtree limitations to assign any role to any user, leading to privilege escalation.","url":"https://insights.sbomify.com/GHSA-394j-x37r-2q27/"}