VulnerabilityPublished 15 Oct 2021Updated 30 May 2025

CVE-2021-41320: A technical user has hardcoded credentials in Wallstreet Suite TRM 7.4.83 (64-bit edition) with higher

Source CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AC:L/AV:L/A:N/C:H/I:N/PR:L/S:U/UI:N

Attack Complexity: Low
Attack Vector: Local
Availability: None
Confidentiality: High
Integrity: None
Privileges Required: Low
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Oct 2021
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should first verify whether the privileged technical user account password has been changed from any default or installation-time value. Implement strict credential management policies that enforce immediate password changes during installation and regular rotation thereafter. Conduct thorough audits to identify any instances of default or weak credentials in the Wallstreet Suite TRM environment. Limit local access to systems running this software to trusted personnel only, and employ network segmentation to reduce the attack surface. Implement robust monitoring and alerting for unusual access patterns or privilege escalations related to the technical user account. If possible, request or develop patches or updates from the vendor that remove or better secure the privileged account credentials. Additionally, consider deploying multi-factor authentication for administrative access to further reduce the risk of credential misuse. Finally, ensure that incident response plans include scenarios involving credential compromise to enable rapid containment and remediation.

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).

Impact

For European organizations using Wallstreet Suite TRM 7.4.83, this vulnerability could lead to unauthorized disclosure of sensitive financial or transactional data due to the high confidentiality impact. Since the privileged account has elevated rights, an attacker exploiting this flaw could access critical information or potentially escalate privileges further. The local attack vector means that attackers would need some form of access to the internal network or system, which could be achieved via compromised user accounts or insider threats. The medium severity reflects that while the vulnerability does not directly affect system availability or integrity, the confidentiality breach could have significant regulatory and reputational consequences, especially under GDPR and other European data protection laws. Financial institutions and organizations handling sensitive market or transaction risk management data would be particularly at risk, as exposure of such data could lead to financial loss, regulatory penalties, and erosion of client trust. The vendor's claim that the password can be changed reduces the risk if organizations have implemented proper installation and credential management practices. However, failure to do so could leave systems vulnerable to exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:39 UTC

Technical details

References

Community reviews

Related threats