{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-10095 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-10095 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10095 is a medium-severity SQL injection vulnerability in Proximus sp. z o.o. SMSEagle, published on 9 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10095 and fix it if it is affected.\n\nWhat it is: CVE-2025-10095 is a medium-severity SQL injection vulnerability in Proximus sp. z o.o. SMSEagle, published on 9 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-10095 in the wild and no public exploit code.\n\nAffected product: Proximus sp. z o.o. SMSEagle. 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-10095/ (Markdown: https://insights.sbomify.com/CVE-2025-10095/index.md)","id":"CVE-2025-10095","markdown":"https://insights.sbomify.com/CVE-2025-10095/index.md","name":"CVE-2025-10095","record":{"aliases":["GHSA-p2rh-v47g-x486"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SMSEagle firmware","requires_auth":"none","summary":"SQL injection in SMSEagle firmware allows attackers to manipulate the SMPP server database via unsanitized input.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL injection vulnerability has been identified in the SMPP server component of the SMSEagle firmware, specifically affecting the handling of certain parameters within the server's database interactions. The vulnerability is isolated to the SMPP server, which operates with its own dedicated database, separate from the main software's database. This isolation limits the scope of the vulnerability to the SMPP server's operations. The vulnerability arises from improper sanitization of user input in the SMPP server's scripts.\n\nThis issue has been fixed in version 6.11.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection in SMPP component of SMSEagle firmware","id":"CVE-2025-10095","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SimStudioAI sim route.ts server-side request forgery","id":"CVE-2025-10096"},"packages":[],"prev":{"headline":"Improper Validation of Specified Quantity in Input in GitLab","id":"CVE-2025-10094"},"products":["SMSEagle"],"published":"2025-09-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-09-11","vendors":["Proximus sp. z o.o."]},"summary":"SQL injection in SMSEagle firmware allows attackers to manipulate the SMPP server database via unsanitized input.","url":"https://insights.sbomify.com/CVE-2025-10095/"}