{"answers":{"affected":"2 open source packages ship an affected version, including ibexa/fieldtype-richtext.","exploited":"There is no known exploitation of GHSA-cj3w-g42v-wcj6 in the wild and no public exploit code.","fix":"Upgrade ibexa/fieldtype-richtext to 4.6.19 or later.","what":"GHSA-cj3w-g42v-wcj6 is a vulnerability in ibexa/fieldtype-richtext, published on 10 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-cj3w-g42v-wcj6 and fix it if it is affected.\n\nWhat it is: GHSA-cj3w-g42v-wcj6 is a vulnerability in ibexa/fieldtype-richtext, published on 10 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-cj3w-g42v-wcj6 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ibexa/fieldtype-richtext (Packagist): affected from 4.6.0-beta1; fixed in 4.6.19\n- ibexa/fieldtype-richtext (Packagist): affected from 4.6.0-beta1; fixed in 4.6.19\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-cj3w-g42v-wcj6/ (Markdown: https://insights.sbomify.com/GHSA-cj3w-g42v-wcj6/index.md)","id":"GHSA-cj3w-g42v-wcj6","markdown":"https://insights.sbomify.com/GHSA-cj3w-g42v-wcj6/index.md","name":"GHSA-cj3w-g42v-wcj6","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ibexa RichText fieldtype","requires_auth":"low_privilege","summary":"An attacker with editor privileges can exploit XXE in RichText fields to read server files, requiring a patch to remove unsafe XML elements.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nThis security advisory resolves a vulnerability in the RichText field type. By entering a maliciously crafted input into the RichText XML, an attacker could perform an attack using XML external entity (XXE) injection, which might be able to read files on the server. To exploit this vulnerability the attacker would need to already have edit permission to content with RichText fields, which typically means Editor role or higher. The fix removes unsafe elements from XML code, while preserving safe elements.\n\nIf you have a stored XXE attack in your content drafts, the fix prevents it from extracting data both during editing and preview. However, if such an attack has already been published and the result is stored in the content, it is unfortunately not possible to detect and remove it by automatic means.\n\n### Credits\nThis vulnerability was discovered and reported to Ibexa by Dennis Henke, Thorsten Niephaus, Marat Aytuganov, and Stephan Sekula of [Compass Security Deutschland GmbH](https://www.compass-security.com/en/). We thank them for reporting it responsibly to us.\n\n### Patches\n- See \"Patched versions\"\n- https://github.com/ibexa/fieldtype-richtext/commit/823cba6b5ee2e81d7d74e622ce42c1451e8e1337\n\n### Workarounds\n- Exploitation requires edit access to RichText content. If you can trust your editors, and you don't grant edit permission to any externals, you are not at risk in practice.\n\n### References\n- https://developers.ibexa.co/security-advisories/ibexa-sa-2025-002-xxe-vulnerability-in-richtext","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/fieldtype-richtext allows access to external entities in XML","id":"GHSA-cj3w-g42v-wcj6","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xxe","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["4.6.19"],"introduced":["4.6.0-beta1"],"last_affected":[],"package":"ibexa/fieldtype-richtext","purl":null,"source":"GHSA-cj3w-g42v-wcj6"},{"ecosystem":"Packagist","fixed":["4.6.19"],"introduced":["4.6.0-beta1"],"last_affected":[],"package":"ibexa/fieldtype-richtext","purl":"pkg:composer/ibexa/fieldtype-richtext","source":"GHSA-cj3w-g42v-wcj6"}],"products":null,"published":"2025-04-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":"An attacker with editor privileges can exploit XXE in RichText fields to read server files, requiring a patch to remove unsafe XML elements.","url":"https://insights.sbomify.com/GHSA-cj3w-g42v-wcj6/"}