Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-69871: n/a

0
High
VulnerabilityCVE-2025-69871cvecve-2025-69871
Published: Wed Feb 11 2026 (02/11/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

A race condition vulnerability exists in MedusaJS Medusa v2.12.2 and earlier in the registerUsage() function of the promotion module. The function performs a non-atomic read-check-update operation when enforcing promotion usage limits. This allows unauthenticated remote attackers to bypass usage limits by sending concurrent checkout requests, resulting in unlimited redemptions of limited-use promotional codes and potential financial loss.

AI-Powered Analysis

AILast updated: 02/19/2026, 14:09:47 UTC

Technical Analysis

CVE-2025-69871 identifies a race condition vulnerability in the MedusaJS e-commerce platform, specifically affecting version 2.12.2 and earlier. The flaw exists in the registerUsage() function within the promotion module, which is responsible for enforcing usage limits on promotional codes. The vulnerability stems from a non-atomic sequence of operations: the function reads the current usage count, checks it against the allowed limit, and then updates the count. Because these steps are not performed atomically, concurrent checkout requests can exploit this timing gap to bypass usage limits. An attacker can send multiple simultaneous checkout requests using the same promotional code, causing the system to incorrectly allow more redemptions than intended. This can lead to unlimited use of limited-use promotions, resulting in financial losses for merchants. The vulnerability requires no authentication or user interaction but has a high attack complexity due to the need to coordinate concurrent requests precisely. The CVSS v3.1 score of 8.1 reflects the high impact on confidentiality, integrity, and availability, as well as the network attack vector and lack of privileges required. While no public exploits are known, the vulnerability represents a significant risk to organizations relying on MedusaJS for their e-commerce operations, particularly those heavily dependent on promotional campaigns. The underlying issue is a classic example of CWE-362 (Race Condition), highlighting the importance of atomic operations in concurrent environments.

Potential Impact

The primary impact of CVE-2025-69871 is financial loss due to unauthorized unlimited redemption of limited-use promotional codes. This undermines the integrity of promotional campaigns, potentially causing significant revenue leakage and damaging merchant trust. The vulnerability also affects availability indirectly by potentially overwhelming backend systems with fraudulent transactions. Confidentiality is impacted as the attacker can manipulate transaction data and usage counts. Organizations relying on MedusaJS for e-commerce may face reputational damage, customer dissatisfaction, and increased operational costs to investigate and remediate fraudulent activities. The ease of exploitation without authentication increases the threat level, especially for high-traffic online stores where concurrent checkout attempts can be automated. The scope includes all deployments of vulnerable MedusaJS versions using the promotion module with usage limits, which may be widespread given MedusaJS's growing adoption in modern e-commerce platforms.

Mitigation Recommendations

To mitigate CVE-2025-69871, organizations should immediately upgrade MedusaJS to a version where this race condition is fixed once available. In the absence of an official patch, implement concurrency controls such as database-level locking or atomic transactions around the registerUsage() function to ensure the read-check-update sequence is atomic. Employ rate limiting and request throttling on checkout endpoints to reduce the feasibility of concurrent exploitation attempts. Monitor logs for unusual patterns of promotional code usage, especially rapid or simultaneous redemptions. Consider implementing additional server-side validation to cross-check usage counts before finalizing transactions. Engage with the MedusaJS community or maintainers to track patch releases and security advisories. Finally, conduct thorough testing of promotion modules under concurrent load to detect similar race conditions proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-01-09T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 698cce794b57a58fa1b3e290

Added to database: 2/11/2026, 6:46:17 PM

Last enriched: 2/19/2026, 2:09:47 PM

Last updated: 2/21/2026, 12:15:18 AM

Views: 14

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats