{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32869 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32869 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32869 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE, published on 19 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32869 and fix it if it is affected.\n\nWhat it is: CVE-2026-32869 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE, published on 19 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32869 in the wild and no public exploit code.\n\nAffected product: OPEXUS eCASE. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-32869/ (Markdown: https://insights.sbomify.com/CVE-2026-32869/index.md)","id":"CVE-2026-32869","markdown":"https://insights.sbomify.com/CVE-2026-32869/index.md","name":"CVE-2026-32869","record":{"aliases":["GHSA-qx35-58q7-q7x6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OPEXUS eComplaint eCASE","requires_auth":"low_privilege","summary":"An authenticated attacker can inject XSS payloads via the Organization Name field, potentially hijacking victim sessions in OPEXUS eComplaint and eCASE.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"ecase_ecomplaint","vendor":"opexustech"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of the \"Name of Organization\" field when filling out case information. An authenticated attacker can inject an XSS payload which is executed in the context of a victim's session when they visit the case information page.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"OPEXUS eComplaint and eCASE XSS via Name of Organization field","id":"CVE-2026-32869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Kirby has XML injection in its XML creator toolkit","id":"CVE-2026-32870"},"packages":[],"prev":{"headline":"OPEXUS eComplaint and eCASE XSS via my information","id":"CVE-2026-32868"},"products":["eCASE","eComplaint"],"published":"2026-03-19","related":[{"cvss_score":9.2,"headline":"OPEXUS eComplaint and eCase insecure password reset","id":"CVE-2026-32865","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":8.7,"headline":"OPEXUS eComplaint IDOR","id":"CVE-2026-22235","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":5.3,"headline":"OPEXUS eComplaint unauthenticated file upload","id":"CVE-2026-32867","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":5.1,"headline":"OPEXUS eComplaint and eCase stored XSS via profile first and last name","id":"CVE-2026-32866","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":5.1,"headline":"OPEXUS eComplaint and eCASE XSS via my information","id":"CVE-2026-32868","kev_date_added":null,"published":"2026-03-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-19","vendors":["OPEXUS"]},"summary":"An authenticated attacker can inject XSS payloads via the Organization Name field, potentially hijacking victim sessions in OPEXUS eComplaint and eCASE.","url":"https://insights.sbomify.com/CVE-2026-32869/"}