Paymenter doesn't reset email verification status after email change
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-44584
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 20:05 UTC · Revision 1
Source evidence
Paymenter doesn't reset email verification status after email change
core-osv · Original sourcePublished 20 Jul 2026, 19:58 UTC
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.
osv:CVE-2026-44584
Complete source record
{
"id": "5fd8d37f13271a335c461b19a388ec9f83e0e7edf1d62afcd3cf7e51e2e89eda",
"url": "https://osv.dev/vulnerability/CVE-2026-44584",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Paymenter doesn't reset email verification status after email change",
"summary": "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.",
"evidence": "osv:CVE-2026-44584",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-44584",
"aliases": [
"CVE-2026-44584",
"GHSA-rv89-wch8-c574"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/paymenter/paymenter",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "0005e4993a1ac780e6c13028632f15c50b6c3679"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.5.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.5.0"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v1.4.6",
"v1.4.5",
"v1.4.4",
"v1.4.3",
"v1.4.2",
"v1.4.1",
"v1.4.0",
"v1.3.4",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.10",
"v1.2.9",
"v1.2.8",
"v1.2.7",
"v1.2.6",
"v1.2.5",
"v1.2.4",
"v1.2.3",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.1",
"v1.1.0",
"v1.0.4",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44584.json"
}
}
],
"modified": "2026-10-28T02:30:23.179686154Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44584.json",
"https://github.com/Paymenter/Paymenter/security/advisories/GHSA-rv89-wch8-c574",
"https://nvd.nist.gov/vuln/detail/CVE-2026-44584"
],
"provider_metadata": {
"cwe_ids": [
"CWE-345"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44584.json"
}
},
"related_cves": [
{
"value": "CVE-2026-44584",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489614,
"published_at": "2026-07-20T19:58:49.126+00:00"
}