VulnerabilityPublished 22 Mar 2026Updated 23 Mar 2026

CVE-2026-4547: mickasmt next-saas-stripe-starter · Business Logic Errors

Affects mickasmt next-saas-stripe-starterSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
mickasmtnext-saas-stripe-starter	Affected =1.0.0	Fixed in–

AI-suggested

To mitigate CVE-2026-4547, organizations should first conduct a thorough code review of the generateUserStripe function and related payment processing logic to ensure strict validation and authorization of the priceId parameter. Implement server-side checks to verify that priceId values correspond to valid, authorized subscription tiers or products and that users are entitled to select them. Employ input sanitization and enforce business rules that prevent manipulation of payment parameters. Integrate comprehensive logging and monitoring to detect anomalous payment or subscription activities indicative of exploitation attempts. If possible, update to a patched version of the next-saas-stripe-starter once released by the vendor or apply custom patches to fix the logic flaw. Additionally, consider implementing multi-factor authentication and rate limiting on payment endpoints to reduce abuse risk. Regularly audit Stripe integration workflows and conduct penetration testing focused on business logic vulnerabilities. Educate development teams on secure coding practices for payment systems to prevent similar issues in future releases.

Description

CVE-2026-4547 is a medium-severity vulnerability in version 1.0.0 of the mickasmt next-saas-stripe-starter product. It arises from business logic errors in the generateUserStripe function within the Checkout Handler component, specifically due to manipulation of the priceId argument. This flaw can be exploited remotely without authentication or user interaction. The vulnerability may allow attackers to bypass intended payment or subscription logic, potentially leading to unauthorized access to paid features or financial discrepancies. No known exploits are currently reported in the wild. Organizations using this starter kit for SaaS Stripe integration should review and patch the affected component to prevent abuse. The CVSS 4.0 score is 5.

Impact

The primary impact of CVE-2026-4547 is financial and operational for organizations deploying the affected next-saas-stripe-starter version 1.0.0. Exploitation can lead to unauthorized access to paid services or subscription tiers without proper payment, resulting in revenue loss and potential abuse of premium features. This undermines the integrity of the payment system and could damage customer trust if fraudulent access occurs. Additionally, business logic flaws are often exploitable in ways that evade traditional security controls, making detection and prevention challenging. Organizations may face increased fraud risk, billing disputes, and potential regulatory scrutiny if customer data or payment processes are compromised. The vulnerability's remote exploitability without authentication broadens the attack surface, allowing attackers to target SaaS applications globally. While availability and confidentiality impacts are minimal, the integrity and financial consequences are significant, especially for startups and businesses relying on Stripe for subscription management.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Mar 2026, 20:04 UTC

Technical details

References

Community reviews

Related threats