Quick answers
- Is CVE-2026-44584 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44584 being exploited in the wild.
- How severe is CVE-2026-44584?
- Medium severity, with a CVSS score of 4.3, published 20 July 2026.
- Which products and versions are affected?
- paymenter/paymenter (Packagist) < 1.5.0, ECOSYSTEM:introduced=0,fixed=1.5.0; Paymenter < 1.5.0.
- Is there a fix for CVE-2026-44584?
- Yes. paymenter/paymenter (Packagist): upgrade to 1.5.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44584 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44584?
- Check whether you run paymenter/paymenter (Packagist) or Paymenter at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- paymenter/paymenter (Packagist): upgrade to 1.5.0 or later
composer require paymenter/paymenter:^1.5.0
Technical details
An insufficient verification of data authenticity (CWE-345) exists in Paymenter's email update logic. When a user modifies their email address, the application does not reset the 'verified' boolean column in the database to false. This allows an authenticated user to first verify a legitimate email and then change it to any arbitrary address while maintaining a verified status without a new confirmation challenge. This bypasses verification-gated features and trust assumptions. The issue is resolved in version 1.5.0.
Affected products
- Paymenter Paymenter < 1.5.0
Identifiers
- CVE-2026-44584
- GHSA-rv89-wch8-c574
Timeline
- 2026-06-10: advisory: GitHub security advisory published by maintainers
- 2026-07-20: disclosed: CVE published to NVD dataset
- 2026-07-20: patched: Fix released in version 1.5.0