# CVE-2025-22371: SQL-injection in admin_login_handler allows unauthenticated user to log in as an administrator in SicommNet BASEC

> Unauthenticated attackers can exploit SQL injection in the login page to bypass authentication and gain administrator access to SicommNet BASEC.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:N/SA:N/AU:Y/V:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2025
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-46h9-fw88-xg28

## What is CVE-2025-22371?

CVE-2025-22371 is a critical SQL injection vulnerability in SicommNet BASEC, published on 14 Apr 2025. 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 SicommNet BASEC (SaaS Service) login page allows an unauthenticated remote attacker to Bypass Authentication and execute arbitrary SQL commands.This issue at least affects BASEC for the date of 14 Dec 2021 onwards. It is very likely that this vulnerability has been present in the solution before that.

The issue was fixed by SicommNet around 11pm on 16 april 2025 (Eastern Time)

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

## Which versions are affected by CVE-2025-22371?


## How do I fix CVE-2025-22371?

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

## Is CVE-2025-22371 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22371 and fix it if it is affected.

What it is: CVE-2025-22371 is a critical SQL injection vulnerability in SicommNet BASEC, published on 14 Apr 2025. 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-2025-22371 in the wild and no public exploit code.

Affected product: SicommNet BASEC. 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-2025-22371/ (Markdown: https://insights.sbomify.com/CVE-2025-22371/index.md)
```

## Sources

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

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