dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10095

MEDIUM · 5.3 CVSS v4.0 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. This issue has been fixed in version 6.11.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in the SMPP server component of SMSEagle firmware due to improper sanitization of user input in database interactions. The SMPP server operates with its own dedicated database, isolating the impact to SMPP server operations only.

MitigationUpgrade SMSEagle firmware to version 6.11 or later to remediate the SQL injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SMPP server is enabled
    Access the SMSEagle web interface and navigate to the SMPP server settings, or check system services for the SMPP daemon process.
    Affected if SMPP server is actively running or configured to start on boot, as the vulnerability only affects SMPP server operations
  2. Check SMSEagle firmware version
    Log into the SMSEagle web interface and locate the firmware version information, typically found in System Status, About, or Settings pages. Alternatively, check the login banner or system information page.
    Affected if The installed firmware version is any version prior to 6.11 (for example, 6.10, 6.09, or earlier)
  3. Confirm SMPP database is in use
    Verify that the SMPP server has been configured with a dedicated database for message handling. Check SMPP configuration for database connection settings.
    Affected if A dedicated SMPP database is configured and active, as the SQL injection occurs in database interactions within this component

You are affected if the SMPP server is enabled and the SMSEagle firmware version is earlier than 6.11, as the SQL injection vulnerability exists in the SMPP server component for versions prior to the 6.11 patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SMSEagle firmware to version 6.11 or later to remediate the SQL injection vulnerability.

Recommended fix Moderate confidence

SMSEagle firmware version 6.11

  1. 1. Identify the current SMSEagle firmware version installed
  2. 2. Download SMSEagle firmware version 6.11 from the official vendor website (www.smseagle.eu)
  3. 3. Review the upgrade instructions provided in the SMSEagle documentation
  4. 4. Perform a backup of the current configuration and database
  5. 5. Apply the firmware upgrade to version 6.11
  6. 6. Verify the upgrade was successful and the SMPP server is functioning correctly
  7. 7. Confirm the SQL injection vulnerability is resolved by testing SMPP server functionality
Caveat Check SMSEagle release notes for any configuration or feature changes between your current version and 6.11

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10095 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data