<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 10:59:41 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-44584</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-44584</link>
      <description>&lt;p&gt;Paymenter is a free and open-source webshop solution for management of hosting services. In versions prior to 1.5.0, 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. 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. Exploitation could potentially result in: misrepresentation of email ownership, bypass of verification-based trust assumptions, and abuse of features gated behind verified status. No direct unauthorized access to other users accounts or data is possible through this issue alone. This issue has been fixed in version 1.5.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Paymenter is a free and open-source webshop solution for management of hosting services. In versions prior to 1.5.0, 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. 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. Exploitation could potentially result in: misrepresentation of email ownership, bypass of verification-based trust assumptions, and abuse of features gated behind verified status. No direct unauthorized access to other users accounts or data is possible through this issue alone. This issue has been fixed in version 1.5.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-44584</guid>
    </item>
    <item>
      <title>GHSA-rv89-wch8-c574 — Paymenter doesn't reset email verification status after email change</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-rv89-wch8-c574</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: paymenter/paymenter&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;This allowed an attacker to:&lt;/p&gt;
&lt;p&gt;- 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&lt;/p&gt;
&lt;p&gt;No verification challenge or confirmation was required for the newly assigned email address.&lt;/p&gt;
&lt;p&gt;### Impact
This vulnerability allows a user to associate a verified account with an email address they do not control, this may result in:&lt;/p&gt;
&lt;p&gt;- Misrepresentation of email ownership
- Bypass of verification-based trust assumptions
- Potential abuse of features gated behind verified status&lt;/p&gt;
&lt;p&gt;No direct unauthorized access to other users accounts or data is possible through this issue alone.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: paymenter/paymenter&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;This allowed an attacker to:&lt;/p&gt;
&lt;p&gt;- 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&lt;/p&gt;
&lt;p&gt;No verification challenge or confirmation was required for the newly assigned email address.&lt;/p&gt;
&lt;p&gt;### Impact
This vulnerability allows a user to associate a verified account with an email address they do not control, this may result in:&lt;/p&gt;
&lt;p&gt;- Misrepresentation of email ownership
- Bypass of verification-based trust assumptions
- Potential abuse of features gated behind verified status&lt;/p&gt;
&lt;p&gt;No direct unauthorized access to other users accounts or data is possible through this issue alone.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-rv89-wch8-c574</guid>
    </item>
  </channel>
</rss>
