{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12932 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12932 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12932 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Jun 2019. 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-2019-12932 and fix it if it is affected.\n\nWhat it is: CVE-2019-12932 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Jun 2019. 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-2019-12932 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-2019-12932/ (Markdown: https://insights.sbomify.com/CVE-2019-12932/index.md)","id":"CVE-2019-12932","markdown":"https://insights.sbomify.com/CVE-2019-12932/index.md","name":"CVE-2019-12932","record":{"aliases":["GHSA-w5fr-p5m9-6cjv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SeedDMS document management","requires_auth":"none","summary":"Attackers can inject malicious scripts via the search autocomplete feature in SeedDMS, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seeddms","vendor":"seeddms"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A stored XSS vulnerability was found in SeedDMS 5.1.11 due to poorly escaping the search result in the autocomplete search form placed in the header of out/out.Viewfolder.php.","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-2019-12932","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-12934"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-12930"},"products":["n/a"],"published":"2019-06-28","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2022-44938","kev_date_added":null,"published":"2022-12-08"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-33223","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-12940","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2018-12941","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2018-12942","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2019-12744","kev_date_added":null,"published":"2019-06-20"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2025-45752","kev_date_added":null,"published":"2025-05-21"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts via the search autocomplete feature in SeedDMS, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2019-12932/"}