{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3004 exists.","fix":"No fix has been published for CVE-2025-3004 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3004 is a medium-severity cross-site scripting vulnerability in Sayski ForestBlog, published on 31 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-3004 and fix it if it is affected.\n\nWhat it is: CVE-2025-3004 is a medium-severity cross-site scripting vulnerability in Sayski ForestBlog, published on 31 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-3004 exists.\n\nAffected product: Sayski ForestBlog. 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-3004/ (Markdown: https://insights.sbomify.com/CVE-2025-3004/index.md)","id":"CVE-2025-3004","markdown":"https://insights.sbomify.com/CVE-2025-3004/index.md","name":"CVE-2025-3004","record":{"aliases":["GHSA-3pmm-gf6j-2r75"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ForestBlog","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary scripts via the search keywords parameter in Sayski ForestBlog, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"forestblog","vendor":"forestblog_project"}],"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 has been found in Sayski ForestBlog up to 20250321 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /search. The manipulation of the argument keywords leads to cross site scripting. 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":"Sayski ForestBlog search cross site scripting","id":"CVE-2025-3004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Sayski ForestBlog Friend Link cross site scripting","id":"CVE-2025-3005"},"packages":[],"prev":{"headline":"ESAFENET CDG UserAjax sql injection","id":"CVE-2025-3003"},"products":["ForestBlog"],"published":"2025-03-31","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-46033","kev_date_added":null,"published":"2022-01-25"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-18964","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":6.3,"headline":"saysky ForestBlog Image Upload img unrestricted upload","id":"CVE-2023-6887","kev_date_added":null,"published":"2023-12-17"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2022-29020","kev_date_added":null,"published":"2022-04-15"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-46034","kev_date_added":null,"published":"2022-01-25"},{"cvss_score":5.1,"headline":"Sayski ForestBlog Friend Link cross site scripting","id":"CVE-2025-3005","kev_date_added":null,"published":"2025-03-31"}],"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-31","vendors":["Sayski"]},"summary":"Remote attackers can execute arbitrary scripts via the search keywords parameter in Sayski ForestBlog, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2025-3004/"}