# CVE-2025-22372: Insecure password storage in SicommNet BASEC

> Attackers with sufficient privileges can extract plain text passwords from SicommNet BASEC SaaS due to insecure storage, leading to account takeover.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:Y/V:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-p8mv-f94r-2px4

## What is CVE-2025-22372?

CVE-2025-22372 is a high-severity vulnerability in SicommNet BASEC, published on 14 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficiently Protected Credentials vulnerability in SicommNet BASEC on SaaS allows Password Recovery.
Passwords are either stored in plain text using reversible encryption, allowing an attacker with sufficient privileges to extract plain text passwords easily.

This issue affects BASEC: from 14 Dec 2021.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2025-22372 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22372 is a high-severity vulnerability in SicommNet BASEC, published on 14 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22372 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-22372/ (Markdown: https://insights.sbomify.com/CVE-2025-22372/index.md)
```

## Sources

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

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