Skip to main content

Webstudio EUVDEUVD-2026-105162

| CVE-2026-113596 LOW
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-20 VulnCheck GHSA-r95x-94xh-ccwh
2.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to Webstudio instance
  2. Exploit
    Obtain victim project UUID
  3. Execution
    Call vulnerable publishedBuilds/findManyByIds tRPC procedure
  4. Impact
    Exfiltrate victim project metadata

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires (1) a valid authenticated user account on the target Webstudio instance (PR:L) and (2) knowledge of another user's project UUID - the AT:P attack requirement in the CVSS vector - because the publishedBuilds and findManyByIds tRPC procedures in versions before 0.256.0 performed no ownership or permission check. No user interaction by the victim is needed. The principal limiting factor is that project UUIDs are unguessable random identifiers, so an attacker must obtain the target UUID out-of-band (shared links, referrals, logs). Impact is further bounded to read-only disclosure of project metadata (publish history, titles, domains, preview images, latest builds) - there is no write access and no exposure of full project source. Fixed in 0.256.0.

Impact

This is a low-priority issue, and the available signals are consistent rather than conflicting. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N) yields a base score of 2.3 (Low): network-reachable but requiring valid authentication (PR:L) and a specific attack requirement (AT:P) - namely prior knowledge of the victim's project UUID - with only limited confidentiality impact and no integrity or availability impact. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The CVE is NOT listed in CISA KEV and no public exploit code is referenced, so exploitation status is 'no public exploit identified at time of analysis.' The source-code diff confirms the root cause (findManyByIds and the publishedBuilds tRPC path lacked an ownership/permission filter, now fixed by filtering on userId OR marketplace-approval and by adding getProjectPermit authorization), which raises confidence that the flaw is real - but the impact ceiling is narrow (read-only exposure of project metadata). Net: a genuine authorization (IDOR) weakness that is correctly scored low; it warrants routine patching rather than emergency response.

Exploit ScenarioDerived

An attacker with a valid authenticated Webstudio account learns another tenant's project UUID (e.g. from a shared URL, referral, or log) and sends a crafted request to the /trpc handler invoking the publishedBuilds or findManyByIds procedures with that UUID. The server, lacking an ownership check in versions before 0.256.0, returns the victim's publish history, titles, domains, preview images, and latest builds. No public exploit code is identified, and exploitation requires authentication plus knowledge of the unguessable UUID, limiting practical abuse.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 20, 2026

Missing authorization in Webstudio before 0.256.0 allows any authenticated user who knows another user's project UUID to read that project's publish history, titles, domains, preview images, and latest builds through the publishedBuilds and findManyByIds tRPC procedures. The issue is rated low severity (CVSS 2.3; assessed CVSS 3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) because exploitation requires a valid account plus an unguessable UUID obtained out-of-band, and impact is limited to read-only metadata disclosure. No public exploit code or CISA KEV entry was identified at time of analysis, and version 0.256.0 contains the vendor fix.

RemediationAI

Upgrade Webstudio to 0.256.0 or later, which contains the ownership and permit checks added in commit 348d049ed2763d2b6c3e00319fa9086ca67c8aa6; see the release notes at https://github.com/webstudio-is/webstudio/releases/tag/0.256.0 and the VulnCheck advisory at https://www.vulncheck.com/advisories/webstudio-before-0.256.0-information-disclosure-via-trpc-publishedbuilds-and-findmanybyids. If immediate upgrade is not possible, reduce exposure by limiting authenticated accounts to trusted users, avoiding publication of project UUIDs in shared links, referrals, and logs, and auditing /trpc access logs for publishedBuilds or findManyByIds requests referencing project IDs not owned by the caller; these are compensating controls only and do not correct the missing authorization check. Blocking the affected tRPC procedures outright would break dashboard and project functionality, so it should be used only as a temporary containment measure.

Affected VersionsENISA

webstudio 0 <0.256.0

Affected Packages

euvd webstudio fix: 0.256.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Webstudio is an open-source website builder whose dashboard and project services expose tRPC procedures backed by a PostgREST client. The affected code path is CWE-639 (Authorization Bypass Through User-Controlled Key): before 0.256.0, the publishedBuilds procedure in packages/project/src/trpc/project-router.ts did not verify that the caller had a view, build, or admin permit for the supplied projectId, and findManyByIds in packages/dashboard/src/db/projects.ts filtered only on isDeleted=false without constraining results to the authenticated userId or to marketplace-approved public templates. The vendor commit 348d049ed2763d2b6c3e00319fa9086ca67c8aa6 adds a getProjectPermit check for view/build/admin and applies a PostgREST or filter matching userId or marketplaceApprovalStatus=APPROVED when a user context is present, while preserving service-context access for templates. The CPE cpe:2.3:a:webstudio-is:webstudio:*:*:*:*:*:*:*:* covers releases prior to 0.256.0.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 2.3 LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 3.1 LOW

Network-reachable tRPC endpoint but requires an authenticated account (PR:L) and knowledge of an unguessable project UUID (AC:H); read-only metadata exposure gives C:L, I:N, A:N.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Webstudio before 0.256.0 contains a missing authorization vulnerability that allows authenticated users to read other users' project data via the publishedBuilds and findManyByIds tRPC procedures. Attackers who know another user's project UUID can query the /trpc handler to retrieve publish history, titles, domains, preview images, and latest builds.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
Low
niche open-source visual website builder, limited production footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

12
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +12
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy