CVE-2026-44584: Paymenter/paymenter Paymenter Doesn't Reset Email Verification Vulnerability

MODERATE
Advisory Identifier: GHSA-rv89-wch8-c574
Share
CVSS 4.3
CWE-287
Published
Advisory Summary

CVE-2026-44584 is a MODERATE (CVSS 4.3) paymenter doesn't reset email verification vulnerability (CWE-287: Improper Authentication) affecting Paymenter/paymenter libraries in the Packagist ecosystem. The issue involves paymenter doesn't reset email verification status after email change. Remediation is available by upgrading affected packages to version 1.5.0.

CVE-2026-44584 at a Glance

CVE Identifier CVE-2026-44584
GHSA Identifier GHSA-rv89-wch8-c574
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-287: Improper Authentication
Affected Product Paymenter/paymenter
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-44584

To remediate this vulnerability, upgrade all affected Paymenter/paymenter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

paymenter/paymenter fixed: 1.5.0 
Upgrade paymenter/paymenter to 1.5.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for paymenter/paymenter

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44584, inspect your project dependencies for Paymenter/paymenter:

inspect dependencies for paymenter/paymenter

Analyze the terminal output to locate any version of Paymenter/paymenter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Paymenter/paymenter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-44584 Affected Paymenter/paymenter Versions

1 component(s)
Fixed Versions:
1.5.0
Product / Package Ecosystem Affected Versions Fixed Version
paymenter/paymenter
 Packagist
< 1.5.0
1.5.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/Paymenter/Paymenter/security/advisories/GHSA-rv89-wch8-c574
Paymenter/paymenter Source Repository REPOSITORY
https://github.com/Paymenter/Paymenter

Frequently Asked Questions

What is CVE-2026-44584?
CVE-2026-44584 is a security vulnerability in Paymenter/paymenter involving Paymenter doesn't reset email verification status after email change under CWE-287: Improper Authentication.
Which Paymenter/paymenter versions are affected?
Affected versions include releases prior to 1.5.0 across affected packages: paymenter/paymenter.
What version fixes CVE-2026-44584?
Upgrading to 1.5.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is paymenter/paymenter affected?
Yes, paymenter/paymenter is affected in releases prior to 1.5.0. Upgrade your dependency to 1.5.0 or later.
What is the CVSS score of CVE-2026-44584?
CVE-2026-44584 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-44584?
CVE-2026-44584 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check Packagist dependencies for CVE-2026-44584?
Run the dependency tree command: 'inspect dependencies for paymenter/paymenter'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rv89-wch8-c574",
  "modified" : "2026-06-22T20:29:41Z",
  "published" : "2026-06-22T20:29:41Z",
  "aliases" : [ "CVE-2026-44584" ],
  "summary" : "Paymenter doesn't reset email verification status after email change",
  "details" : "### Summary\nThe 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.\n\n### Technical Details\nWhen 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.\n\nThis allowed an attacker to:\n\n- Verify an account using a legitimate email address\n- Change the account email to an arbitrary or unowned address\n- Retain the verified status without re-confirmation of the new email\n\nNo verification challenge or confirmation was required for the newly assigned email address.\n\n### Impact\nThis vulnerability allows a user to associate a verified account with an email address they do not control, this may result in:\n\n- Misrepresentation of email ownership\n- Bypass of verification-based trust assumptions\n- Potential abuse of features gated behind verified status\n\nNo direct unauthorized access to other users accounts or data is possible through this issue alone.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "paymenter/paymenter"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Paymenter/Paymenter/security/advisories/GHSA-rv89-wch8-c574"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Paymenter/Paymenter"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-22T20:29:41Z",
    "nvd_published_at" : null
  }
}