{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15002 exists.","fix":"No fix has been published for CVE-2025-15002 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15002 is a medium-severity SQL injection vulnerability in Seacms Seacms, published on 21 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-15002 and fix it if it is affected.\n\nWhat it is: CVE-2025-15002 is a medium-severity SQL injection vulnerability in Seacms Seacms, published on 21 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15002 exists.\n\nAffected product: Seacms Seacms. 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-15002/ (Markdown: https://insights.sbomify.com/CVE-2025-15002/index.md)","id":"CVE-2025-15002","markdown":"https://insights.sbomify.com/CVE-2025-15002/index.md","name":"CVE-2025-15002","record":{"aliases":["GHSA-wm3h-v48w-fqgf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SeaCMS","requires_auth":"none","summary":"Remote attackers can exploit SQL injection in SeaCMS via the page/limit argument to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"seacms","vendor":"seacms"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability has been found in SeaCMS up to 13.3. The affected element is an unknown function of the file js/player/dmplayer/dmku/class/mysqli.class.php. Such manipulation of the argument page/limit leads to sql injection. The attack can be executed 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":"SeaCMS mysqli.class.php sql injection","id":"CVE-2025-15002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"seacms:seacms","products":["seacms:seacms"],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"SeaCMS admin_video.php sql injection","id":"CVE-2025-15003"},"packages":[],"prev":{"headline":"FS Registration Password \u003c= 1.0.1 - Unauthenticated Privilege Escalation via Account Takeover","id":"CVE-2025-15001"},"products":["SeaCMS"],"published":"2025-12-21","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44073","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-44071","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44072","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44074","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-29647","kev_date_added":null,"published":"2025-04-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25516","kev_date_added":null,"published":"2025-02-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25517","kev_date_added":null,"published":"2025-02-25"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-24","vendors":["n/a"]},"summary":"Remote attackers can exploit SQL injection in SeaCMS via the page/limit argument to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2025-15002/"}