# CVE-2024-7407: Weak password encoding in Streamsoft Prestiż

> An attacker with database access can decode stored passwords using a weak custom algorithm, exposing user credentials.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2025
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-g4rq-8hw9-mj8q

## What is CVE-2024-7407?

CVE-2024-7407 is a high-severity vulnerability in Streamsoft Prestiż, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of a custom password encoding algorithm in Streamsoft Prestiż software allows straightforward decoding of passwords using their encoded forms, which are stored in the application's database. One has to know the encoding algorithm, but it can be deduced by observing how password are transformed. 
This issue was fixed in 18.2.377 version of the software.

Weakness: CWE-261 (Weak Encoding for Password)

## Which versions are affected by CVE-2024-7407?


## How do I fix CVE-2024-7407?

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

## Is CVE-2024-7407 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7407 and fix it if it is affected.

What it is: CVE-2024-7407 is a high-severity vulnerability in Streamsoft Prestiż, published on 28 Mar 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-2024-7407 in the wild and no public exploit code.

Affected product: Streamsoft Prestiż. 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-2024-7407/ (Markdown: https://insights.sbomify.com/CVE-2024-7407/index.md)
```

## Sources

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

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