CVE-2026-44584

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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. 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.

CVSS v3
4.3
EG Score
4.3(low)
EPSS
KEV
Not listed

Published

June 22, 2026

Last Modified

June 22, 2026

Vendor Advisories for CVE-2026-44584(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
paymenter/paymenter0.1 ... v1.1.1 (32 versions)1.5.0

Data Freshness Timeline

(refreshed 8× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 18:47 UTCEG score recompute
  2. 2026-07-05 20:03 UTCEG score recompute
  3. 2026-07-04 21:48 UTCEG score recompute
  4. 2026-07-03 23:34 UTCEG score recompute
  5. 2026-07-03 01:20 UTCEG score recompute
  6. 2026-07-02 03:06 UTCEG score recompute
  7. 2026-07-01 04:52 UTCEG score recompute
  8. 2026-06-30 06:37 UTCEG score recompute
  9. 2026-06-29 08:23 UTCEG score recompute
  10. 2026-06-28 10:09 UTCEG score recompute
  11. 2026-06-27 11:55 UTCEG score recompute
  12. 2026-06-26 13:40 UTCEG score recompute
  13. 2026-06-25 15:24 UTCEG score recompute
  14. 2026-06-24 17:10 UTCEG score recompute
  15. 2026-06-23 18:50 UTCEG score recompute
  16. 2026-06-22 20:36 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-44584?
CVE-2026-44584 is a medium vulnerability published on June 22, 2026. 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…
When was CVE-2026-44584 disclosed?
CVE-2026-44584 was first published in the National Vulnerability Database on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-44584?
CVE-2026-44584 has a CVSS v4.0 base score of 4.3 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-44584?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44584, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44584

Explore →

Is Your Infrastructure Affected by CVE-2026-44584?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.