{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-38710 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-38710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-38710 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Aug 2021. 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-2021-38710 and fix it if it is affected.\n\nWhat it is: CVE-2021-38710 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Aug 2021. 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-2021-38710 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-2021-38710/ (Markdown: https://insights.sbomify.com/CVE-2021-38710/index.md)","id":"CVE-2021-38710","markdown":"https://insights.sbomify.com/CVE-2021-38710/index.md","name":"CVE-2021-38710","record":{"aliases":["GHSA-4qj7-wcgp-pm8p"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Yclas CMS","requires_auth":"none","summary":"Attackers can inject persistent scripts via the SITE_NAME parameter in Yclas, potentially leading to session hijacking or malicious actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yclas","vendor":"yclas"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","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":"Static (Persistent) XSS Vulnerability exists in version 4.3.0 of Yclas when using the install/view/form.php script. An attacker can store XSS in the database through the vulnerable SITE_NAME parameter.","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-2021-38710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"In gitit before 0.15.0.0, the Export feature can be exploited to leak information from files.","id":"CVE-2021-38711"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-38709"},"products":["n/a"],"published":"2021-08-18","related":[],"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 persistent scripts via the SITE_NAME parameter in Yclas, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2021-38710/"}