dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-25606

HIGH · 8.7 CVSS v4.0 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable 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 STER. Improper neutralization of input provided by user into multiple Search Filters allows for SQL Injection attacks. It allows an authenticated attacker to view sensitive data such as data belonging to other users, or any other data that the application itself is able to access This issue was fixed in version 9.5.

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 · high confidence

A SQL injection vulnerability exists in STER's search filters where user input is not properly neutralized before being used in SQL queries. An authenticated attacker can exploit this to inject malicious SQL code and access sensitive data belonging to other users or any data the application can access.

MitigationUpgrade to version 9.5 which contains the fix. If immediate upgrade is not possible, implement parameterized queries or prepared statements for all search filter inputs, and add input validation to sanitize user-provided values before database queries.

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
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/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 STER installation and version
    Locate the STER application installation directory and check for version information in metadata files, about dialog, or version configuration. Common locations include installation logs, config files, or the application executable metadata.
    Affected if The installed version of STER is 9.4 or earlier (any version prior to the fixed version 9.5).
  2. Verify search filter functionality is enabled
    Access the STER application and navigate to the search filter feature. Check if search filters are available to authenticated users through the web interface, API, or desktop client.
    Affected if Search filter functionality is active and accessible to at least some authenticated users.
  3. Inspect search filter input handling
    Use the search filter feature with test input (such as simple SQL characters like single quotes) and observe the application's response. Check backend logs for errors or unexpected database behavior. Review application configuration for how search parameters are processed.
    Affected if User-supplied input in search filters appears to be passed directly to database queries without visible sanitization, or the application exhibits unusual behavior with special SQL characters.
  4. Review database query patterns for search filters
    Examine database connection logs, query logs, or application code (if accessible) that handles search filter requests. Look for instances where search parameters are concatenated into SQL strings rather than using parameterized queries.
    Affected if Search filter database interactions use string concatenation for user input instead of parameterized queries or prepared statements.

You are affected if STER version 9.4 or earlier is installed AND the search filter feature is accessible to authenticated users with direct SQL query construction in use.

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 to version 9.5 which contains the fix. If immediate upgrade is not possible, implement parameterized queries or prepared statements for all search filter inputs, and add input validation to sanitize user-provided values before database queries.

Recommended fix Moderate confidence

9.5

  1. 1. Verify current STER software version by accessing the administration panel or checking the application metadata
  2. 2. If the current version is below 9.5, plan for an upgrade to version 9.5
  3. 3. Before upgrading, perform a full backup of the database and application files
  4. 4. Download the version 9.5 release from the official STER vendor distribution channel
  5. 5. Follow the vendor's official upgrade instructions for version 9.5
  6. 6. After upgrading, verify that the SQL injection vulnerability in Search Filters is resolved
  7. 7. Test that the application functions correctly with the new version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25606 — 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-2026-25606 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