Introduction

The Vebto Platform research repository documents a multi-stage unauthenticated remote code execution chain affecting the shared foundation used by products such as BeLink, BeDesk, BeDrive, BeMusic, MTDB, and Architect. The chain combines a social-authentication bypass with unsafe file-storage controls.

A public security-research repository documents the technical findings and proof-of-concept material associated with the issue. The discussion below focuses on the security impact, root cause, affected component, and defensive remediation rather than reproducing weaponized exploitation steps.

Vulnerability Overview

The social login callback processes a user-supplied token without enforcing the application's social-login configuration boundary. After an account and API token are obtained, the file-entry upload functionality can be manipulated through storage parameters that bypass intended PHP-file restrictions.

In simplified terms, the security problem looks like this:

Unauthenticated Request
        │
        ▼
Social Auth Callback
        │
        ▼
Authentication Bypass / Account Creation
        │
        ▼
File Upload Endpoint
        │
        ▼
Storage Parameter Validation Bypass
        │
        ▼
Dangerous File in Public Storage
        │
        ▼
Potential RCE

The important security principle is that untrusted client input must never be allowed to cross an authentication, authorization, filesystem, or code-execution boundary without strict server-side validation.

Why Is This Vulnerability Serious?

The chain is significant because it turns an authentication weakness into a file-upload compromise. Multi-tenant products sharing the same foundation can inherit the same security design flaw.

The potential impact depends on the application's configuration, the privileges of the affected process, and whether vulnerable functionality is exposed to untrusted users.

Root Cause

The documented weaknesses include missing social-provider enablement checks and insufficient validation of storage parameters that determine where uploaded content is written.

A secure implementation should independently verify:

• Authentication and authorization requirements
• The ownership or scope of the requested object
• Input type, format, and allowed values
• Filesystem paths and canonical destinations where applicable
• File type and content where uploads are involved
• That privileged operations cannot be selected through client-controlled parameters
• That sensitive functionality fails closed when validation fails

Affected Versions / Components

The publicly documented affected details are:

These details are based on the public research repository and, where available, the corresponding NVD record. Administrators should verify the exact installed version and deployment configuration before determining exposure.

Public PoC

The associated repository contains research and proof-of-concept material demonstrating the vulnerability.

For defensive research, proof-of-concept code should only be used in an authorized laboratory environment or against systems for which explicit permission has been granted. Production systems should be tested using harmless validation methods whenever possible.

Security Impact

1. Unauthenticated account compromise

Unauthenticated account compromise can become a security concern depending on the deployment and the privileges of the affected component.

2. Arbitrary file upload

Arbitrary file upload can become a security concern depending on the deployment and the privileges of the affected component.

3. Potential remote code execution

Potential remote code execution can become a security concern depending on the deployment and the privileges of the affected component.

4. Application and tenant compromise

Application and tenant compromise can become a security concern depending on the deployment and the privileges of the affected component.

Detection and Mitigation

Administrators should first identify whether the affected component is installed and determine the exact version.

Recommended defensive actions include:

• Update affected Vebto-based products to fixed releases when available.
• Disable unused social-login providers.
• Validate OAuth tokens against the configured provider and application settings.
• Do not trust client-controlled storage parameters.
• Block executable uploads and disable script execution in public storage.

Indicators of Compromise

For incident-response purposes, administrators should review application and web-server logs around the affected functionality.

A useful investigation should examine:

Application / Web Logs
        │
        ├── Unusual Requests to Vulnerable Functions
        ├── Unexpected Authentication Events
        ├── Suspicious File Operations
        ├── Unexpected Account / Role Changes
        ├── Recently Modified Files
        └── Unusual Outbound Connections

Log evidence should be correlated with account activity, filesystem changes, deployment history, and application configuration rather than treated as a single definitive indicator.

Conclusion

The Vebto Platform research repository documents a multi-stage unauthenticated remote code execution chain affecting the shared foundation used by products such as BeLink, BeDesk, BeDrive, BeMusic, MTDB, and Architect. The chain combines a social-authentication bypass with unsafe file-storage controls.

The main lesson is that security-sensitive functionality must enforce authorization and validation on the server side. Client-controlled identifiers, role values, filenames, MIME types, filesystem paths, and template content should never be trusted simply because they originated from an apparently legitimate application workflow.

For security researchers and developers, this issue provides a useful case study in secure application design, particularly around authorization boundaries, file handling, authentication, input validation, and defense-in-depth.

SOURCE: https://github.com/Yucaerin/Vebto-Platform-Unauthenticated-to-RCE-via-Social-Auth-Bypass-diskPrefix-Upload

References:

• No separate CVE reference was identified in the public repository.