Verified-status bypass via stale email verification
Published Jul 20, 2026 · Updated Jul 20, 2026
Improper authentication in Paymenter before 1.5.0 allows remote authenticated users to retain verified status after changing email. The email update path writes the new address without clearing or revalidating the account's verification column, leaving it true. A previously verified account is required; the flaw enables false email-ownership claims and verified-only feature access, but not access to other accounts or data.
Summary
What happened
Improper authentication in Paymenter before 1.5.0 allows remote authenticated users to retain verified status after changing email. The email update path writes the new address without clearing or revalidating the account's verification column, leaving it true. A previously verified account is required; the flaw enables false email-ownership claims and verified-only feature access, but not access to other accounts or data.
The record
- CVE
- CVE-2026-44584
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- Paymenter
- Product
- Paymenter
- Classifications
- T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo