{"items":[{"id":"NVI-00003115","kind":"vulnerability","title":"Paymenter doesn't reset email verification status after email change","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-rv89-wch8-c574","CVE-2026-44584"],"plain_summary":"OSV carries this publisher advisory for paymenter/paymenter. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.5.0 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-004db81a8abe4c0c89d49dad839cce71"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-23T16:04:11.740Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-12d94457a5aa2b5d4d1e92de07437879"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.163%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.05467. Missing scores are unknown.","source_id":"sr-004db81a8abe4c0c89d49dad839cce71"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-331273de18fe89e1efc65d7bfadb9d41","url":"https://github.com/advisories/GHSA-rv89-wch8-c574","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rv89-wch8-c574","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.366Z"},{"id":"sr-12d94457a5aa2b5d4d1e92de07437879","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-44584","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-44584","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:02.489Z"},{"id":"sr-004db81a8abe4c0c89d49dad839cce71","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-44584","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.854Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### 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.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.0"]}],"null_published_at":"2026-11-03T17:49:14.966Z","source_updated_at":"2026-09-10T03:50:50.485Z","source_disclosed_at":"2026-06-22T20:29:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:41.366Z"},{"id":"NVI-00003115","kind":"vulnerability","title":"Paymenter doesn't reset email verification status after email change","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-rv89-wch8-c574","CVE-2026-44584"],"plain_summary":"OSV carries this publisher advisory for paymenter/paymenter. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.5.0 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-06536cf9f1f84363ad589551d11ffea8"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-23T16:04:11.740Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-12d94457a5aa2b5d4d1e92de07437879"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.163%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.05478. Missing scores are unknown.","source_id":"sr-06536cf9f1f84363ad589551d11ffea8"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-331273de18fe89e1efc65d7bfadb9d41","url":"https://github.com/advisories/GHSA-rv89-wch8-c574","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rv89-wch8-c574","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.366Z"},{"id":"sr-12d94457a5aa2b5d4d1e92de07437879","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-44584","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-44584","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:02.489Z"},{"id":"sr-06536cf9f1f84363ad589551d11ffea8","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-44584","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.279Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### 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.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.0"]}],"null_published_at":"2026-11-02T20:21:07.821Z","source_updated_at":"2026-09-10T03:50:50.485Z","source_disclosed_at":"2026-06-22T20:29:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:41.366Z"},{"id":"NVI-00003115","kind":"vulnerability","title":"Paymenter doesn't reset email verification status after email change","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-rv89-wch8-c574","CVE-2026-44584"],"plain_summary":"OSV carries this publisher advisory for paymenter/paymenter. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.5.0 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-12d94457a5aa2b5d4d1e92de07437879"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-23T16:04:11.740Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-12d94457a5aa2b5d4d1e92de07437879"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-331273de18fe89e1efc65d7bfadb9d41","url":"https://github.com/advisories/GHSA-rv89-wch8-c574","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rv89-wch8-c574","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.366Z"},{"id":"sr-12d94457a5aa2b5d4d1e92de07437879","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-44584","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-44584","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:02.489Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### 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.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.0"]}],"null_published_at":"2026-11-01T14:34:07.529Z","source_updated_at":"2026-09-10T03:50:50.485Z","source_disclosed_at":"2026-06-22T20:29:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:41.366Z"},{"id":"NVI-00003115","kind":"vulnerability","title":"Paymenter doesn't reset email verification status after email change","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rv89-wch8-c574","CVE-2026-44584"],"plain_summary":"OSV carries this publisher advisory for paymenter/paymenter. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.5.0 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-331273de18fe89e1efc65d7bfadb9d41","url":"https://github.com/advisories/GHSA-rv89-wch8-c574","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rv89-wch8-c574","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.366Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-331273de18fe89e1efc65d7bfadb9d41"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### 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.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.0"]}],"null_published_at":"2026-10-31T22:12:38.475Z","source_updated_at":"2026-09-10T03:50:50.485Z","source_disclosed_at":"2026-06-22T20:29:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:41.366Z"}],"next_cursor":null,"snapshot_revision":"42594"}