VulnerabilityPublished 22 Mar 2026Updated 23 Mar 2026

CVE-2026-4548: mickasmt next-saas-stripe-starter · Improper Authorization

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, 11:52 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 10% 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:L/VI:L/VA:L/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: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 30 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–
npmnext-saas-stripe-starter`pkg:npm/next-saas-stripe-starter`Other threats	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-4548, developers and organizations should implement strict authorization checks within the updateUserrole function to ensure that only users with appropriate administrative privileges can modify user roles. Input validation should be enforced on userId and role parameters to prevent unauthorized manipulation. Employ role-based access control (RBAC) frameworks that verify permissions server-side before processing role changes. Audit and log all role update attempts to detect suspicious activities promptly. If possible, upgrade to a patched version of next-saas-stripe-starter once available or apply custom patches to fix the authorization logic. Additionally, conduct thorough security reviews of all functions handling user roles and permissions in the application. Employ runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block unauthorized role modification attempts. Educate development teams on secure coding practices related to authorization and access control.

Description

CVE-2026-4548 is a medium severity vulnerability in mickasmt next-saas-stripe-starter version 1.0.0, specifically in the updateUserrole function of actions/update-user-role.ts. The flaw allows improper authorization due to manipulation of userId and role parameters, enabling an attacker to potentially escalate privileges or modify user roles without proper permission. The vulnerability can be exploited remotely without user interaction and requires low privileges, making it accessible to authenticated attackers with minimal barriers. Although no known exploits are currently reported in the wild, the risk of unauthorized role changes could lead to privilege escalation and unauthorized access to sensitive functions. Organizations using this starter kit for SaaS applications integrating Stripe should prioritize patching or implementing strict access controls. Countries with significant SaaS development ecosystems and Stripe usage are at higher risk. Mitigation involves enforcing strict authorization checks on role updates, validating input parameters, and monitoring role change activities.

Impact

The primary impact of CVE-2026-4548 is unauthorized privilege escalation through improper role updates, which can lead to compromised user accounts with elevated permissions. This can result in unauthorized access to sensitive data, manipulation of billing or subscription details, and potential disruption of SaaS services relying on next-saas-stripe-starter. Organizations using this starter kit may face risks including data breaches, financial fraud, and loss of customer trust. Since the vulnerability is remotely exploitable and requires only low privileges, attackers could leverage it to escalate their access without needing to compromise higher privileged accounts initially. The scope affects all deployments of version 1.0.0 of the product, which may be used globally by SaaS developers integrating Stripe. Although no active exploits are known, the vulnerability could be targeted in supply chain attacks or by attackers scanning for vulnerable SaaS applications. The medium severity rating reflects moderate impact but significant risk due to the nature of role-based access control violations.

Summary

CVE-2026-4548 identifies an improper authorization vulnerability in the mickasmt next-saas-stripe-starter software, version 1.0.0. The vulnerability resides in the updateUserrole function within the actions/update-user-role.ts file. This function improperly authorizes requests that manipulate the userId and role arguments, allowing an attacker to change user roles without sufficient permission checks. The vulnerability is exploitable remotely and does not require user interaction, but it does require the attacker to have some level of privileges (PR:L). The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The flaw could enable privilege escalation or unauthorized role modification, potentially compromising the application's access control model. No patches or known exploits are currently documented, but the vulnerability's presence in a starter kit used for SaaS applications integrating Stripe payments means it could be widely impactful if exploited. The vulnerability highlights the importance of robust authorization checks on sensitive operations like role updates in multi-tenant SaaS environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats