{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52670 exists.","fix":"No fix has been published for CVE-2025-52670 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52670 is a high-severity missing authorization vulnerability in Revive-Adserver Revive Adserver, published on 20 Nov 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-52670 and fix it if it is affected.\n\nWhat it is: CVE-2025-52670 is a high-severity missing authorization vulnerability in Revive-Adserver Revive Adserver, published on 20 Nov 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-52670 exists.\n\nAffected product: Revive-Adserver Revive Adserver. 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-52670/ (Markdown: https://insights.sbomify.com/CVE-2025-52670/index.md)","id":"CVE-2025-52670","markdown":"https://insights.sbomify.com/CVE-2025-52670/index.md","name":"CVE-2025-52670","record":{"aliases":["GHSA-9pgh-m953-mhjq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ad server software","requires_auth":"low_privilege","summary":"Authenticated users can delete banners belonging to other accounts due to missing authorization checks in Revive Adserver.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"revive_adserver","vendor":"revive-adserver"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-862","name":"Missing Authorization"}],"description":"Missing authorization check in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes users on the system to delete banners owned by other accounts","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":"Missing authorization in Revive Adserver","id":"CVE-2025-52670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"revive-adserver:revive_adserver","products":["revive-adserver:revive_adserver"],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Revive Adserver","id":"CVE-2025-52671"},"packages":[],"prev":{"headline":"Information disclosure in Revive Adserver","id":"CVE-2025-52669"},"products":["Revive Adserver"],"published":"2025-11-20","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Revive Adserver All versions before 3.2.3","id":"CVE-2016-9124","kev_date_added":null,"published":"2017-03-28"},{"cvss_score":9.8,"headline":"Auth bypass in Revive Adserver All versions before 3.2.3","id":"CVE-2016-9125","kev_date_added":null,"published":"2017-03-28"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2017-5830","kev_date_added":null,"published":"2017-03-03"},{"cvss_score":9,"headline":"Other in Revive Adserver All versions before 3.2.5 and 4.0.0","id":"CVE-2016-9470","kev_date_added":null,"published":"2017-03-28"},{"cvss_score":8.8,"headline":"Code injection in Adserver","id":"CVE-2026-50741","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":8.8,"headline":"Missing authorization in Revive Adserver","id":"CVE-2025-48986","kev_date_added":null,"published":"2025-11-20"},{"cvss_score":8.8,"headline":"SQL injection in Revive Adserver","id":"CVE-2025-52664","kev_date_added":null,"published":"2025-10-30"}],"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-12-01","vendors":["Revive"]},"summary":"Authenticated users can delete banners belonging to other accounts due to missing authorization checks in Revive Adserver.","url":"https://insights.sbomify.com/CVE-2025-52670/"}