GHSA-8R29-2MP2-PMRW
Vulnerability from github – Published: 2026-10-06 16:17 – Updated: 2026-10-06 16:17Impact
When using the Stripe payment adapter, an order confirmation could be processed more than once under certain conditions.
You are affected if:
- You use @payloadcms/plugin-ecommerce with the Stripe payment adapter.
Deployments that do not use the Stripe payment flow are not affected.
Patches
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds
Ensure Stripe order confirmations can only be processed once. This is a temporary mitigation; upgrading to a patched version is recommended.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@payloadcms/plugin-ecommerce"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.90.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "@payloadcms/plugin-ecommerce"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0-canary.0"
},
{
"fixed": "4.0.0-canary.34"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-105850"
],
"database_specific": {
"cwe_ids": [
"CWE-837"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-06T16:17:54Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Impact\nWhen using the Stripe payment adapter, an order confirmation could be processed more than once under certain conditions.\n\nYou are affected if:\n- You use `@payloadcms/plugin-ecommerce` with the Stripe payment adapter.\n\nDeployments that do not use the Stripe payment flow are not affected.\n\n## Patches\nUsers should upgrade Payload packages to `\u003e= 3.90.0` or `\u003e= 4.0.0-canary.34`.\n\n## Workarounds\nEnsure Stripe order confirmations can only be processed once. This is a temporary mitigation; upgrading to a patched version is recommended.",
"id": "GHSA-8r29-2mp2-pmrw",
"modified": "2026-10-06T16:17:54Z",
"published": "2026-10-06T16:17:54Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/payloadcms/payload/security/advisories/GHSA-8r29-2mp2-pmrw"
},
{
"type": "WEB",
"url": "https://github.com/payloadcms/payload/commit/6c0c4dc9b4ce1ac87b03fbb5dd7356b8559cbc4e"
},
{
"type": "PACKAGE",
"url": "https://github.com/payloadcms/payload"
},
{
"type": "WEB",
"url": "https://github.com/payloadcms/payload/releases/tag/v3.90.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Payload Ecommerce has an order confirmation validation issue"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.