CVE-2026-44584 is a medium-severity improper authentication vulnerability in paymenter/paymenter (composer), affecting versions < 1.5.0. It is fixed in 1.5.0.
Summary The email update functionality fails to invalidate the existing verification state when a user changes their email address, allowing a verified account to retain its verified status after switching to an unverified or unowned email address. Technical Details When a user updated their email address, the system did not reset or revalidate the associated email verification status. As a result, the verification column remained set to “true” even after the email address was changed. This allowed an attacker to: Verify an account using a legitimate email address Change the account email to an arbitrary or unowned address Retain the verified status without re-confirmation of the new email No verification challenge or confirmation was required for the newly assigned email address. Impact This vulnerability allows a user to associate a verified account with an email address they do not control, this may result in: Misrepresentation of email ownership Bypass of verification-based trust assumptions Potential abuse of features gated behind verified status No direct unauthorized access to other users accounts or data is possible through this issue alone.
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-2026-44584 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low 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 (1.5.0). Upgrading removes the vulnerable code path.
composer
paymenter/paymenter (< 1.5.0)paymenter/paymenter → 1.5.0 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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 instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-44584 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-44584 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-44584 in your environment →Upgrade paymenter/paymenter to 1.5.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-44584 is a medium-severity improper authentication vulnerability in paymenter/paymenter (composer), affecting versions < 1.5.0. It is fixed in 1.5.0. The application does not adequately verify the identity of a user, device, or process before granting access.
CVE-2026-44584 has a CVSS score of 4.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.
paymenter/paymenter (composer) versions < 1.5.0 is affected.
Yes. CVE-2026-44584 is fixed in 1.5.0. Upgrade to this version or later.
Whether CVE-2026-44584 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
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.
Upgrade paymenter/paymenter to 1.5.0 or later.