{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2364 exists.","fix":"No fix has been published for CVE-2025-2364 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2364 is a medium-severity cross-site scripting vulnerability in lenve VBlog, published on 17 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-2364 and fix it if it is affected.\n\nWhat it is: CVE-2025-2364 is a medium-severity cross-site scripting vulnerability in lenve VBlog, published on 17 Mar 2025. Any signed-in user can exploit it over the network, 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-2364 exists.\n\nAffected product: lenve VBlog. 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-2364/ (Markdown: https://insights.sbomify.com/CVE-2025-2364/index.md)","id":"CVE-2025-2364","markdown":"https://insights.sbomify.com/CVE-2025-2364/index.md","name":"CVE-2025-2364","record":{"aliases":["GHSA-r2xw-g69f-4fpr"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"VBlog web application","requires_auth":"low_privilege","summary":"Remote attackers can inject malicious scripts via article content in VBlog, 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":"vblog","vendor":"lenve"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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 was found in lenve VBlog up to 1.0.0. Affected by this vulnerability is the function addNewArticle of the file blogserver/src/main/java/org/sang/service/ArticleService.java. The manipulation of the argument mdContent/htmlContent leads to cross site scripting. The attack can be launched 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":null,"headline":"lenve VBlog ArticleService.java addNewArticle cross site scripting","id":"CVE-2025-2364","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"crmeb_java WeChatMessageController.java webHook xml external entity reference","id":"CVE-2025-2365"},"packages":[],"prev":{"headline":"lenve VBlog ArticleController.java uploadImg path traversal","id":"CVE-2025-2363"},"products":["VBlog"],"published":"2025-03-17","related":[{"cvss_score":5.3,"headline":"lenve VBlog WebSecurityConfig.java configure access control","id":"CVE-2025-3398","kev_date_added":null,"published":"2025-04-08"},{"cvss_score":5.3,"headline":"lenve VBlog ArticleController.java uploadImg path traversal","id":"CVE-2025-2363","kev_date_added":null,"published":"2025-03-17"}],"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-17","vendors":["lenve"]},"summary":"Remote attackers can inject malicious scripts via article content in VBlog, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2025-2364/"}