VulnerabilityPublished 20 Mar 2025Updated 15 Oct 2025

CVE-2024-9431: transformeroptimus/superagi · Unverified Password Change

Affects transformeroptimus/superagiSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.0 base score

6.5Medium

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable 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.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2025
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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
GitHubtransformeroptimus/superagi`pkg:github/transformeroptimus/superagi`Other threats	Affected =0.0.14	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Implement strict role-based access control (RBAC) to ensure only authorized administrators can change user passwords.
Monitor and audit password change events to detect anomalous activities promptly.
Restrict access to transformeroptimus/superagi interfaces to trusted networks and users.
Apply vendor patches immediately once available; engage with the vendor for timeline and interim fixes.
Enforce multi-factor authentication (MFA) to reduce the risk of compromised credentials being exploited.
Conduct regular security reviews and penetration tests focusing on privilege escalation vectors.
Educate users about the risk of unauthorized password changes and encourage reporting of suspicious behavior.
If patching is delayed, consider disabling password change functionality for non-administrative users as a temporary control.

Description

In version v0.0.14 of transformeroptimus/superagi, there is an improper privilege management vulnerability. After logging into the system, users can change the passwords of other users, leading to potential account takeover.

Impact

For European organizations, the vulnerability could lead to unauthorized account takeovers within transformeroptimus/superagi deployments, potentially allowing attackers to manipulate user credentials and gain elevated access. This can disrupt business processes, lead to insider-like attacks, and undermine trust in identity management. Sectors relying on this software for automation or AI-driven workflows may experience operational disruptions or data integrity issues. Although confidentiality and availability are not directly impacted, the integrity breach can cascade into broader security incidents if attackers leverage compromised accounts to access sensitive data or systems. The medium severity rating indicates a significant but not critical risk, emphasizing the need for timely remediation especially in regulated industries such as finance, healthcare, and critical infrastructure prevalent in Europe.

CWE-620Unverified Password Change (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.
Architecture and Design
When prompting for a password change, force the user to provide the original password in addition to the new password.
Architecture and Design
Do not use "forgotten password" functionality. But if you must, ensure that you are only providing information to the actual user, e.g. by using an email address or challenge question that the legitimate user already provided in the past; do not allow the current user to change this identity information until the…
OWASP Cheat Sheets
Choosing and Using Security Questions (opens in a new tab)
Forgot Password (opens in a new tab)
Credential Stuffing Prevention (opens in a new tab)
Authentication (opens in a new tab)
Transport Layer Protection (opens in a new tab)
OWASP ASVS 4.0.3
V2.1.6 (opens in a new tab)
V2.2.3 (opens in a new tab)
V2.1.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

huntr.com/bounties/9b33d7c1-ed0a-4f5b-a378-694570fd990b (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:05 UTC

WeaknessesCWE-620

Technical details

References

Community reviews

Related threats