# CVE-2026-2397: SQLi in AdamPOS' MobilMen 20T

> Attackers can execute arbitrary SQL commands in AdamPOS MobilMen 20T, potentially reading or modifying database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-r958-fxrc-p879

## What is CVE-2026-2397?

CVE-2026-2397 is a critical SQL injection vulnerability in Adam Retail Automation Ltd. MobilMen 20T, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-2397?


## How do I fix CVE-2026-2397?

No fix has been published for CVE-2026-2397 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2397 being exploited?

There is no known exploitation of CVE-2026-2397 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2397 and fix it if it is affected.

What it is: CVE-2026-2397 is a critical SQL injection vulnerability in Adam Retail Automation Ltd. MobilMen 20T, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2397 in the wild and no public exploit code.

Affected product: Adam Retail Automation Ltd. MobilMen 20T. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2397/ (Markdown: https://insights.sbomify.com/CVE-2026-2397/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2397
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2397
- OSV: https://osv.dev/vulnerability/CVE-2026-2397

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2397/
Summaries are generated and may contain mistakes; the official description above is the record.