{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22233 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22233 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22233 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE Audit, published on 8 Jan 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-22233 and fix it if it is affected.\n\nWhat it is: CVE-2026-22233 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE Audit, published on 8 Jan 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-22233 in the wild and no public exploit code.\n\nAffected product: OPEXUS eCASE Audit. 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-22233/ (Markdown: https://insights.sbomify.com/CVE-2026-22233/index.md)","id":"CVE-2026-22233","markdown":"https://insights.sbomify.com/CVE-2026-22233/index.md","name":"CVE-2026-22233","record":{"aliases":["GHSA-xgp7-wwhw-7q3c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Audit management software","requires_auth":"low_privilege","summary":"Authenticated attackers can inject JavaScript into audit fields, executing it for other users viewing project costs, potentially leading to session hijacking.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"ecase_audit","vendor":"opexustech"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/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 eCASE Audit allows an authenticated attacker to save JavaScript as a comment in the \"Estimated Staff Hours\" field. The JavaScript is executed whenever another user visits the Project Cost tab. Fixed in OPEXUS eCASE Audit 11.14.2.0.","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 eCASE Audit Project Cost stored XSS","id":"CVE-2026-22233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OPEXUS eCasePortal unauthenticated IDOR","id":"CVE-2026-22234"},"packages":[],"prev":{"headline":"OPEXUS eCASE Audit Project Setup stored XSS","id":"CVE-2026-22232"},"products":["eCASE Audit"],"published":"2026-01-08","related":[{"cvss_score":7.2,"headline":"OPEXUS eCASE Audit incorrect access control","id":"CVE-2026-22230","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":4.8,"headline":"OPEXUS eCASE Audit Document Check Out stored XSS","id":"CVE-2026-22231","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":4.8,"headline":"OPEXUS eCASE Audit Project Setup stored XSS","id":"CVE-2026-22232","kev_date_added":null,"published":"2026-01-08"}],"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-01-08","vendors":["OPEXUS"]},"summary":"Authenticated attackers can inject JavaScript into audit fields, executing it for other users viewing project costs, potentially leading to session hijacking.","url":"https://insights.sbomify.com/CVE-2026-22233/"}