CVE-2025-29773: Froxlor allows Multiple Accounts to Share the Same Email Address Leading to Potential Privilege Escalation or Account Takeover

Published Mar 11, 2025
·
Updated

Summary 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 admin@froxlor.com, others can also create an account using the same email). This creates potential issues with account identification and security.

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

Other sources

Froxlor is open-source server administration software. A vulnerability in versions prior to 2.2.6 allows users (such as resellers or customers) to create accounts with the same email address as an existing account. This creates potential issues with account identification and security. 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. 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. Version 2.2.6 fixes the issue.

MITRE

Affected Software

2 affected componentsFixes available
composer/froxlor/froxlor<=2.2.5
2.2.6
Froxlor Froxlor=2.2.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/froxlor/froxlor to a version that resolves this vulnerability.

    Fixed in 2.2.6
  2. Upgrade

    Upgrade froxlor to a version that resolves this vulnerability.

    Fixed in 2.2.6

Event History

Mar 11, 2025
Advisory Published
via GitHub·08:30 PM
Mar 13, 2025
CVE Published
via MITRE·05:07 PM
Data Sourced
via MITRE·05:07 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyAffected Software
Oct 27, 57234
Event
via NVD·09:21 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-29773?

CVE-2025-29773 is classified as a medium severity vulnerability due to the risk of multiple user accounts sharing the same email address.

2

How do I fix CVE-2025-29773?

To fix CVE-2025-29773, upgrade to Froxlor version 2.2.6 or newer.

3

What are the consequences of CVE-2025-29773?

The consequence of CVE-2025-29773 is that it may lead to account management issues and impersonation risks.

4

Who is affected by CVE-2025-29773?

Users who are using Froxlor versions up to 2.2.5 are affected by CVE-2025-29773.

5

Can user data be compromised due to CVE-2025-29773?

Yes, user data can potentially be compromised, as multiple accounts with the same email can confuse permissions and account access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203