dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2397

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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
Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Adam Retail Automation Ltd. MobilMen 20T allows SQL Injection. This issue affects MobilMen 20T: from v3 through 10072026. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 Adam Retail Automation Ltd. MobilMen 20T (versions v3 through 10072026) allows attackers to inject malicious SQL commands via unsanitized input. With a CVSS score of 9.8, this critical flaw could allow unauthenticated attackers to exfiltrate, modify, or destroy database contents including sensitive retail transaction data.

MitigationSince the vendor did not respond to disclosure, immediate options include deploying WAF rules to block SQL injection patterns, network isolating the application, and engaging the vendor through alternative channels. Long-term remediation requires either a vendor-supplied patch or migration to a supported retail automation platform.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm MobilMen 20T is installed
    Locate the Adam Retail Automation Ltd. MobilMen application in your environment. Check for its installation directory, service name, or running processes that indicate this product is present.
    Affected if The product MobilMen 20T from Adam Retail Automation Ltd. is found in your environment.
  2. Determine the installed version
    Access the application's version information through its About dialog, configuration files, or installer records. Compare the version against the affected range: v3 through 10072026.
    Affected if The installed version falls within v3 through 10072026.
  3. Identify database interaction points
    Review the application configuration, log files, or documentation to determine how it connects to and interacts with its database. Look for database connection strings, SQL query logs, or ORM configuration files.
    Affected if The application uses direct SQL queries to interact with a database.
  4. Assess network accessibility of the SQL interface
    Determine whether the application's database-facing interfaces are exposed to network access beyond trusted internal networks. Check firewall rules, access controls, and application binding configurations.
    Affected if The SQL interface is accessible from networks or hosts that are not strictly trusted.
  5. Check for parameterized query implementation
    Review application source code, configuration, or deployment files to verify whether SQL queries are constructed using parameterized queries or prepared statements rather than string concatenation.
    Affected if SQL queries are built using string concatenation or dynamic query construction without parameterized methods.

You are likely affected if MobilMen 20T version v3 through 10072026 is installed, the application uses direct SQL queries, and those database interfaces are accessible to potential attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor did not respond to disclosure, immediate options include deploying WAF rules to block SQL injection patterns, network isolating the application, and engaging the vendor through alternative channels. Long-term remediation requires either a vendor-supplied patch or migration to a supported retail automation platform.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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