{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2040 exists.","fix":"No fix has been published for CVE-2025-2040 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2040 is a medium-severity code injection vulnerability in zhijiantianya ruoyi-vue-pro, published on 6 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-2040 and fix it if it is affected.\n\nWhat it is: CVE-2025-2040 is a medium-severity code injection vulnerability in zhijiantianya ruoyi-vue-pro, published on 6 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2040 exists.\n\nAffected product: zhijiantianya ruoyi-vue-pro. 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-2040/ (Markdown: https://insights.sbomify.com/CVE-2025-2040/index.md)","id":"CVE-2025-2040","markdown":"https://insights.sbomify.com/CVE-2025-2040/index.md","name":"CVE-2025-2040","record":{"aliases":["GHSA-hv2c-wf43-5v98"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"RuoYi Vue Pro","requires_auth":"low_privilege","summary":"Remote attackers with permissions can execute arbitrary code via template injection in the BPM model deployment endpoint.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ruoyi-vue-pro","vendor":"iocoder"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-791","name":"Incomplete Filtering of Special Elements"},{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"A vulnerability classified as critical was found in zhijiantianya ruoyi-vue-pro 2.4.1. Affected by this vulnerability is an unknown functionality of the file /admin-api/bpm/model/deploy. The manipulation leads to improper neutralization of special elements used in a template engine. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"zhijiantianya ruoyi-vue-pro deploy special elements used in a template engine","id":"CVE-2025-2040","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"s-a-zhd Ecommerce-Website-using-PHP shop.php sql injection","id":"CVE-2025-2041"},"packages":[],"prev":{"headline":"code-projects Blood Bank Management System delete_members.php sql injection","id":"CVE-2025-2039"},"products":["ruoyi-vue-pro"],"published":"2025-03-06","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2022-37158","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":5.3,"headline":"YunaiV ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10988","kev_date_added":null,"published":"2025-09-26"},{"cvss_score":5.3,"headline":"YunaiV ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10276","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":5.3,"headline":"YunaiV ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10278","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":5.3,"headline":"zhijiantianya ruoyi-vue-pro Material Upload Interface upload-permanent path traversal","id":"CVE-2025-2742","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":5.3,"headline":"zhijiantianya ruoyi-vue-pro Material Upload Interface upload-temporary path traversal","id":"CVE-2025-2743","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":5.3,"headline":"zhijiantianya ruoyi-vue-pro Material Upload Interface upload-news-image path traversal","id":"CVE-2025-2744","kev_date_added":null,"published":"2025-03-25"}],"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-03-06","vendors":["zhijiantianya"]},"summary":"Remote attackers with permissions can execute arbitrary code via template injection in the BPM model deployment endpoint.","url":"https://insights.sbomify.com/CVE-2025-2040/"}