{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52664 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52664 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52664 is a high-severity SQL injection vulnerability in Revive-Adserver Revive Adserver, published on 30 Oct 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-52664 and fix it if it is affected.\n\nWhat it is: CVE-2025-52664 is a high-severity SQL injection vulnerability in Revive-Adserver Revive Adserver, published on 30 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52664 in the wild and no public exploit code.\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-52664/ (Markdown: https://insights.sbomify.com/CVE-2025-52664/index.md)","id":"CVE-2025-52664","markdown":"https://insights.sbomify.com/CVE-2025-52664/index.md","name":"CVE-2025-52664","record":{"aliases":["GHSA-7pmf-h72m-cp8q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Ad server software","requires_auth":"low_privilege","summary":"Logged-in users can exploit SQL injection in Revive Adserver to access information or disrupt service.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"revive_adserver","vendor":"revive-adserver"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/CR:X/IR:X/AR:X","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection in Revive Adserver 6.0.0 causes potential disruption or information access when specifically crafted payloads are sent by logged in users","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL injection in Revive Adserver","id":"CVE-2025-52664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"revive-adserver:revive_adserver","products":["revive-adserver:revive_adserver"],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in UniFi Access Application","id":"CVE-2025-52665"},"packages":[],"prev":{"headline":"Security feature bypass in UniFi Talk G3 Phones","id":"CVE-2025-52663"},"products":["Revive Adserver"],"published":"2025-10-30","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"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-01","vendors":["Revive"]},"summary":"Logged-in users can exploit SQL injection in Revive Adserver to access information or disrupt service.","url":"https://insights.sbomify.com/CVE-2025-52664/"}