CVE-2025-29773

the vulnerability is that users (such as resellers or customers) are able to create accounts with the same email address as an existing account (e.g., if the admin has [email protected], others can also create an account using the same email). This creates potential issues with account identification and security.

Local/Authenticated: This vulnerability can be exploited by authenticated users (e.g., reseller, customer) who can create accounts with the same email address that has already been used by another account, such as the admin.
Email-based: The attack vector is email-based, as the system does not prevent multiple accounts from registering the same email address, leading to possible conflicts and security issues.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2025-29773 has a CVSS score of 5.8 (Medium). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.6); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-29773? CVE-2025-29773 is a medium-severity improper authentication vulnerability in froxlor/froxlor (composer), affecting versions <= 2.2.5. It is fixed in 2.2.6. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2025-29773? CVE-2025-29773 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of froxlor/froxlor are affected by CVE-2025-29773? froxlor/froxlor (composer) versions <= 2.2.5 is affected.
4. Is there a fix for CVE-2025-29773? Yes. CVE-2025-29773 is fixed in 2.2.6. Upgrade to this version or later.
5. Is CVE-2025-29773 exploitable, and should I be worried? Whether CVE-2025-29773 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-29773 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-29773? Upgrade froxlor/froxlor to 2.2.6 or later.