CVE-2026-25509

Summary

The authentication implementation in CI4MS is vulnerable to email enumeration. An unauthenticated attacker can determine whether an email address is registered in the system by analyzing the application's response during the password reset process.

Vulnerability Details

• The password reset flow returns different responses based on whether the provided email address exists in the database or not.
• If the email is registered, the system typically returns a success message (e.g., "Password reset link has been sent").

If the email is not registered, the system returns an error message (e.g., "User not found" or a different HTTP status code).

This discrepancy allows attackers to programmatically "enumerate" or confirm valid user emails, which can then be used for targeted phishing attacks or brute-force attempts.

Steps to Reproduce

1. Navigate to the password reset page of the CI4MS installation.
2. Enter an email address that you know is not registered (e.g., [email protected]) and submit. Note the response message/code.
3. Enter an email address that is registered (e.g., an admin or test account) and submit. Note the different response.
4. The difference between these two responses confirms the enumeration vulnerability.

Suggested Mitigation

Implement a uniform, generic response for all password reset requests, regardless of whether the email exists. Recommended message: "If an account is associated with this email address, a password reset link has been sent."

CVE-2026-25509 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. 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 (0.28.5.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-25509? CVE-2026-25509 is a medium-severity security vulnerability in ci4-cms-erp/ci4ms (composer), affecting versions < 0.28.5.0. It is fixed in 0.28.5.0.
2. How severe is CVE-2026-25509? CVE-2026-25509 has a CVSS score of 5.3 (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 ci4-cms-erp/ci4ms are affected by CVE-2026-25509? ci4-cms-erp/ci4ms (composer) versions < 0.28.5.0 is affected.
4. Is there a fix for CVE-2026-25509? Yes. CVE-2026-25509 is fixed in 0.28.5.0. Upgrade to this version or later.
5. Is CVE-2026-25509 exploitable, and should I be worried? Whether CVE-2026-25509 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-2026-25509 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-2026-25509? Upgrade ci4-cms-erp/ci4ms to 0.28.5.0 or later.