{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8520 exists.","fix":"No fix has been published for CVE-2025-8520 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8520 is a medium-severity server-side request forgery vulnerability in givanz Vvveb, published on 4 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8520 and fix it if it is affected.\n\nWhat it is: CVE-2025-8520 is a medium-severity server-side request forgery vulnerability in givanz Vvveb, published on 4 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8520 exists.\n\nAffected product: givanz Vvveb. 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-8520/ (Markdown: https://insights.sbomify.com/CVE-2025-8520/index.md)","id":"CVE-2025-8520","markdown":"https://insights.sbomify.com/CVE-2025-8520/index.md","name":"CVE-2025-8520","record":{"aliases":["GHSA-7r9g-v72r-prmj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Vvveb CMS","requires_auth":"high_privilege","summary":"Remote attackers can exploit a server-side request forgery vulnerability in the Vvveb Drag-and-Drop Editor to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"vvveb","vendor":"vvveb"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A vulnerability classified as critical was found in givanz Vvveb up to 1.0.5. This vulnerability affects unknown code of the file /vadmin123/?module=editor/editor of the component Drag-and-Drop Editor. The manipulation of the argument url leads to server-side request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.0.6 is able to address this issue. The patch is identified as f684f3e374d04db715730fc4796e102f5ebcacb2. It is recommended to upgrade the affected component.","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":"givanz Vvveb Drag-and-Drop Editor editor server-side request forgery","id":"CVE-2025-8520","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"givanz Vvveb Add Type post-types cross site scripting","id":"CVE-2025-8521"},"packages":[],"prev":{"headline":"givanz Vvveb Drag-and-Drop Editor editor information disclosure","id":"CVE-2025-8519"},"products":["Vvveb"],"published":"2025-08-04","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-44022","kev_date_added":null,"published":"2025-05-12"},{"cvss_score":6.9,"headline":"givanz Vvveb Image information disclosure","id":"CVE-2025-11028","kev_date_added":null,"published":"2025-09-26"},{"cvss_score":5.3,"headline":"givanz Vvveb Code Editor functions.php sanitizeFileName path traversal","id":"CVE-2025-12203","kev_date_added":null,"published":"2025-10-27"},{"cvss_score":5.3,"headline":"givanz Vvveb cross-site request forgery","id":"CVE-2025-11029","kev_date_added":null,"published":"2025-09-26"},{"cvss_score":5.3,"headline":"givanz Vvveb login.tpl cross site scripting","id":"CVE-2025-9728","kev_date_added":null,"published":"2025-08-31"},{"cvss_score":5.3,"headline":"givanz Vvveb media.php unrestricted upload","id":"CVE-2025-9397","kev_date_added":null,"published":"2025-08-24"},{"cvss_score":5.3,"headline":"givanz Vvveb session fixiation","id":"CVE-2025-8517","kev_date_added":null,"published":"2025-08-04"}],"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-08-05","vendors":["givanz"]},"summary":"Remote attackers can exploit a server-side request forgery vulnerability in the Vvveb Drag-and-Drop Editor to access internal resources.","url":"https://insights.sbomify.com/CVE-2025-8520/"}