# CVE-2021-41320: Hardcoded credentials in n/a

> A technical user account with elevated privileges exists in Wallstreet Suite TRM, potentially allowing unauthorized access if default credentials are not changed.

- **Severity:** Medium 5.5 (`CVSS:3.1/AC:L/AV:L/A:N/C:H/I:N/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2021
- **Updated:** 30 May 2025
- **Also known as:** GHSA-qc22-6662-58rj

## What is CVE-2021-41320?

CVE-2021-41320 is a medium-severity vulnerability in n/a, published on 15 Oct 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A technical user has hardcoded credentials in Wallstreet Suite TRM 7.4.83 (64-bit edition) with higher privilege than the average authenticated user. NOTE: the vendor disputes this because the password is not hardcoded (it can be changed during installation or at any later time).

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2021-41320?

It affects 1 product.


Products: Iongroup Wallstreet Suite.

## How do I fix CVE-2021-41320?

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

## Is CVE-2021-41320 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41320 and fix it if it is affected.

What it is: CVE-2021-41320 is a medium-severity vulnerability in n/a, published on 15 Oct 2021. 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-2021-41320 in the wild and no public exploit code.

Affected product: n/a. 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-2021-41320/ (Markdown: https://insights.sbomify.com/CVE-2021-41320/index.md)
```

## Sources

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

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