CVE-2026-44584: Paymenter doesn't reset email verification status after email change
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.
Published Jun 22, 2026
Affected packages
paymenter/paymenter
- Ecosystem
- Composer (PHP)
- Affected
- < 1.5.0
- Fixed in
- 1.5.0
- Check
composer show paymenter/paymenter
Advisory details
From the GitHub Advisory Database (CC BY 4.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.
Credited to ljskatt, CorwinDev.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-103026
Paymenter: Unauthenticated arbitrary method invocation in Livewire components
high8.1Nov 20, 2026CVE-2026-71537
Paymenter has a credit-refund double-spend race condition in service downgrade (doUpgrade)
medium6.5Sep 18, 2026CVE-2026-47198
Paymenter has URL parameter injection that bypasses paid plan limits at checkout
high8.5Jun 30, 2026CVE-2026-55219
Paymenter has race condition in payWithCredit() that enables credit double-spend
medium5.3Jun 30, 2026CVE-2025-58048
Paymenter vulnerable to Remote Code Execution via public file uploads
critical9.9Jun 22, 2026CVE-2026-44583
Paymenter has Blind Unauthenticated SSRF on the Paypal gateway module
medium5.3Jun 22, 2026
