{"items":[{"id":"NVI-00004985","kind":"vulnerability","title":"Paymenter has race condition in payWithCredit() that enables credit double-spend","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-pgcq-8grm-5rx9","CVE-2026-55219"],"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.5 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"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-254bb5c606d8b67f2f424744e5c59006"],"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":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-98daa252635433106fa530059455d117"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.214%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11708. Missing scores are unknown.","source_id":"sr-254bb5c606d8b67f2f424744e5c59006"}],"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-7bf0dc8c31b73975595a8f7cede1326a","url":"https://github.com/advisories/GHSA-pgcq-8grm-5rx9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgcq-8grm-5rx9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"},{"id":"sr-98daa252635433106fa530059455d117","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55219","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55219","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:31.710Z"},{"id":"sr-254bb5c606d8b67f2f424744e5c59006","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-55219","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.788Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### Summary\nThe credit payment implementation in `app/Livewire/Invoices/Show.php` executes a pessimistic row lock (`lockForUpdate()`) outside of an active database transaction. Because MySQL/MariaDB requires an enclosing transaction to enforce row-level locks, the guard is ineffective. Concurrent payment requests can exploit this race condition to read the same credit balance simultaneously, allowing users to pay multiple invoices using the same credit balance.\n\n### Technical Details\nThe issue occurs because the application attempts to lock the user's credit balance row in the database (`lockForUpdate()`) without opening a database transaction. In database systems like MySQL, a row lock only works inside a formal transaction; without one, the lock is completely ignored.\n\nBecause there is no active lock, two payment requests sent at the exact same millisecond can look at the database at the same time. Both requests see the original credit balance, decide it is sufficient, and approve the payment.\n\n### Impact\nThis race condition allows any authenticated user with a valid credit balance to bypass balance restrictions and settle multiple pending invoices simultaneously for the cost of ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.5"]}],"null_published_at":"2026-11-08T19:53:33.554Z","source_updated_at":"2026-09-10T03:51:09.283Z","source_disclosed_at":"2026-06-30T19:11:24.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:30.990Z"},{"id":"NVI-00004985","kind":"vulnerability","title":"Paymenter has race condition in payWithCredit() that enables credit double-spend","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-pgcq-8grm-5rx9","CVE-2026-55219"],"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.5 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"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-613bf4ee742224964c3c91d7becf49df"],"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":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-98daa252635433106fa530059455d117"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.214%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11689. Missing scores are unknown.","source_id":"sr-613bf4ee742224964c3c91d7becf49df"}],"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-7bf0dc8c31b73975595a8f7cede1326a","url":"https://github.com/advisories/GHSA-pgcq-8grm-5rx9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgcq-8grm-5rx9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"},{"id":"sr-98daa252635433106fa530059455d117","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55219","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55219","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:31.710Z"},{"id":"sr-613bf4ee742224964c3c91d7becf49df","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-55219","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### Summary\nThe credit payment implementation in `app/Livewire/Invoices/Show.php` executes a pessimistic row lock (`lockForUpdate()`) outside of an active database transaction. Because MySQL/MariaDB requires an enclosing transaction to enforce row-level locks, the guard is ineffective. Concurrent payment requests can exploit this race condition to read the same credit balance simultaneously, allowing users to pay multiple invoices using the same credit balance.\n\n### Technical Details\nThe issue occurs because the application attempts to lock the user's credit balance row in the database (`lockForUpdate()`) without opening a database transaction. In database systems like MySQL, a row lock only works inside a formal transaction; without one, the lock is completely ignored.\n\nBecause there is no active lock, two payment requests sent at the exact same millisecond can look at the database at the same time. Both requests see the original credit balance, decide it is sufficient, and approve the payment.\n\n### Impact\nThis race condition allows any authenticated user with a valid credit balance to bypass balance restrictions and settle multiple pending invoices simultaneously for the cost of ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.5"]}],"null_published_at":"2026-11-06T15:18:11.502Z","source_updated_at":"2026-09-10T03:51:09.283Z","source_disclosed_at":"2026-06-30T19:11:24.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:30.990Z"},{"id":"NVI-00004985","kind":"vulnerability","title":"Paymenter has race condition in payWithCredit() that enables credit double-spend","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pgcq-8grm-5rx9","CVE-2026-55219"],"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.5 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"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-613bf4ee742224964c3c91d7becf49df"],"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":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.214%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11689. Missing scores are unknown.","source_id":"sr-613bf4ee742224964c3c91d7becf49df"}],"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-7bf0dc8c31b73975595a8f7cede1326a","url":"https://github.com/advisories/GHSA-pgcq-8grm-5rx9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgcq-8grm-5rx9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"},{"id":"sr-613bf4ee742224964c3c91d7becf49df","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-55219","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### Summary\nThe credit payment implementation in `app/Livewire/Invoices/Show.php` executes a pessimistic row lock (`lockForUpdate()`) outside of an active database transaction. Because MySQL/MariaDB requires an enclosing transaction to enforce row-level locks, the guard is ineffective. Concurrent payment requests can exploit this race condition to read the same credit balance simultaneously, allowing users to pay multiple invoices using the same credit balance.\n\n### Technical Details\nThe issue occurs because the application attempts to lock the user's credit balance row in the database (`lockForUpdate()`) without opening a database transaction. In database systems like MySQL, a row lock only works inside a formal transaction; without one, the lock is completely ignored.\n\nBecause there is no active lock, two payment requests sent at the exact same millisecond can look at the database at the same time. Both requests see the original credit balance, decide it is sufficient, and approve the payment.\n\n### Impact\nThis race condition allows any authenticated user with a valid credit balance to bypass balance restrictions and settle multiple pending invoices simultaneously for the cost of ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.5"]}],"null_published_at":"2026-11-01T01:45:38.537Z","source_updated_at":"2026-09-10T03:51:09.283Z","source_disclosed_at":"2026-06-30T19:11:24.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:30.990Z"},{"id":"NVI-00004985","kind":"vulnerability","title":"Paymenter has race condition in payWithCredit() that enables credit double-spend","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pgcq-8grm-5rx9","CVE-2026-55219"],"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.5 for paymenter/paymenter. Confirm the publisher’s latest guidance.","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"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-7bf0dc8c31b73975595a8f7cede1326a","url":"https://github.com/advisories/GHSA-pgcq-8grm-5rx9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pgcq-8grm-5rx9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.990Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7bf0dc8c31b73975595a8f7cede1326a"],"technology":"paymenter/paymenter","known_exclusions":[],"conditions_summary":"### Summary\nThe credit payment implementation in `app/Livewire/Invoices/Show.php` executes a pessimistic row lock (`lockForUpdate()`) outside of an active database transaction. Because MySQL/MariaDB requires an enclosing transaction to enforce row-level locks, the guard is ineffective. Concurrent payment requests can exploit this race condition to read the same credit balance simultaneously, allowing users to pay multiple invoices using the same credit balance.\n\n### Technical Details\nThe issue occurs because the application attempts to lock the user's credit balance row in the database (`lockForUpdate()`) without opening a database transaction. In database systems like MySQL, a row lock only works inside a formal transaction; without one, the lock is completely ignored.\n\nBecause there is no active lock, two payment requests sent at the exact same millisecond can look at the database at the same time. Both requests see the original credit balance, decide it is sufficient, and approve the payment.\n\n### Impact\nThis race condition allows any authenticated user with a valid credit balance to bypass balance restrictions and settle multiple pending invoices simultaneously for the cost of ","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.5.5"]}],"null_published_at":"2026-10-31T22:12:57.150Z","source_updated_at":"2026-09-10T03:51:09.283Z","source_disclosed_at":"2026-06-30T19:11:24.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:30.990Z"}],"next_cursor":null,"snapshot_revision":"42594"}