{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3397 exists.","fix":"No fix has been published for CVE-2025-3397 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3397 is a medium-severity cross-site scripting vulnerability in YzmCMS, published on 8 Apr 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-3397 and fix it if it is affected.\n\nWhat it is: CVE-2025-3397 is a medium-severity cross-site scripting vulnerability in YzmCMS, published on 8 Apr 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3397 exists.\n\nAffected product: YzmCMS. 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-3397/ (Markdown: https://insights.sbomify.com/CVE-2025-3397/index.md)","id":"CVE-2025-3397","markdown":"https://insights.sbomify.com/CVE-2025-3397/index.md","name":"CVE-2025-3397","record":{"aliases":["GHSA-vh9f-239f-vjhp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"YzmCMS","requires_auth":"none","summary":"Remote attackers can inject malicious scripts via the gourl argument in YzmCMS, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"yzmcms","vendor":"yzmcms"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A vulnerability classified as problematic has been found in YzmCMS 7.1. Affected is an unknown function of the file message.tpl. The manipulation of the argument gourl leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"YzmCMS message.tpl cross site scripting","id":"CVE-2025-3397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"lenve VBlog WebSecurityConfig.java configure access control","id":"CVE-2025-3398"},"packages":[],"prev":{"headline":"Incorrect Authorization in GitLab","id":"CVE-2025-3396"},"products":["YzmCMS"],"published":"2025-04-08","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-11554","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2022-23383","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-23595","kev_date_added":null,"published":"2023-08-11"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-23384","kev_date_added":null,"published":"2022-02-15"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-23888","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-19951","kev_date_added":null,"published":"2021-09-23"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-20015","kev_date_added":null,"published":"2018-12-10"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-08","vendors":["n/a"]},"summary":"Remote attackers can inject malicious scripts via the gourl argument in YzmCMS, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2025-3397/"}