{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-54965 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-54965 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54965 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-54965 and fix it if it is affected.\n\nWhat it is: CVE-2025-54965 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-54965 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2025-54965/ (Markdown: https://insights.sbomify.com/CVE-2025-54965/index.md)","id":"CVE-2025-54965","markdown":"https://insights.sbomify.com/CVE-2025-54965/index.md","name":"CVE-2025-54965","record":{"aliases":["GHSA-684r-2x4m-wrjh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SOCET GXP","requires_auth":"none","summary":"An attacker can execute arbitrary JavaScript in a victim's browser via a malicious link due to unsanitized job ID parameters in SOCET GXP.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"socet_gxp","vendor":"baesystems"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"An XSS issue was discovered in BAE SOCET GXP before 4.6.0.2. The SOCET GXP Job Status Service does not properly sanitize the job ID parameter before using it in the job status page. An attacker who is able to social engineer a user into clicking a malicious link may be able to execute arbitrary JavaScript in the victim's browser.","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":"Cross-site scripting in n/a","id":"CVE-2025-54965","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-54966"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-54964"},"products":["n/a"],"published":"2025-10-27","related":[{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2025-54968","kev_date_added":null,"published":"2025-10-27"},{"cvss_score":8.4,"headline":"Command injection in n/a","id":"CVE-2025-54964","kev_date_added":null,"published":"2025-10-23"},{"cvss_score":6.5,"headline":"XML external entity in n/a","id":"CVE-2025-54967","kev_date_added":null,"published":"2025-10-27"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2025-54970","kev_date_added":null,"published":"2025-10-27"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2025-54963","kev_date_added":null,"published":"2025-10-23"},{"cvss_score":6.1,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-54969","kev_date_added":null,"published":"2025-10-27"}],"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":"2025-10-27","vendors":["n/a"]},"summary":"An attacker can execute arbitrary JavaScript in a victim's browser via a malicious link due to unsanitized job ID parameters in SOCET GXP.","url":"https://insights.sbomify.com/CVE-2025-54965/"}