GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
Check your stack
GHSA-rv89-wch8-c574medium4.3

Paymenter doesn't reset email verification status after email change

Impact

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.

Source excerpt · OSV

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

paymenter/paymenter Packagist
Affected rangeRecorded fix
Earlier releases before 1.5.0Ecosystem versions1.5.0

Version evidence: OSV · GHSA-rv89-wch8-c574

View original version evidence (32 explicit versions)

Original source description

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.

References