/

CVE-2026-22788

Severity:

HIGH RISK

(8.2)

Missing Authentication in WebErpMesV2 Sensitive API

CVE-2026-22788

Analyzed

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized Data Exposure and Manipulation

Severity:

HIGH RISK

(8.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

WebErpMesV2 prior to 1.19 exposes multiple business-critical API endpoints without enforcing authentication.

An unauthenticated remote attacker can read sensitive data such as companies, quotes, orders, tasks, and whiteboards, and gains limited write access to create company records and fully manipulate collaboration whiteboards whenever these APIs are reachable over the network.

Affected context

This vulnerability affects WebErpMesV2 deployments that expose the application's HTTP API to users or other systems over a network.

It occurs where sensitive routes for business objects (companies, quotes, orders, tasks, whiteboards, and related collaboration features) are accessible without an authentication middleware or equivalent access control layer.

Any environment where these endpoints are reachable from untrusted networks, such as the public internet or shared internal networks, is at elevated risk.

Exploit preconditions

  • Attack surface: Network-accessible WebErpMesV2 HTTP API
  • Required access: Unauthenticated remote access (no valid account or credentials required)
  • Trigger point: Directly invoking sensitive API endpoints for company data, quotes, orders, tasks, and whiteboards
  • Why exploitation is possible: The application fails to enforce authentication on selected endpoints, allowing requests to succeed solely based on network reachability rather than user identity or session state

Why this happens

The issue stems from missing authentication checks on multiple sensitive API endpoints, aligning with CWE-306: Missing Authentication for Critical Function.

In this design pattern, endpoint routing and controller logic handle business operations—such as reading or modifying companies, quotes, orders, tasks, and whiteboards—without passing through a central authentication middleware or explicit identity verification.

As a result, the system treats any incoming request as implicitly trusted, enabling anonymous users to access operations that should be restricted to authenticated and typically authorized accounts.

Potential impact

  • Unauthenticated reading of business-critical data such as companies, quotes, orders, and tasks
  • Exposure of operational and planning information that can reveal pricing, customer relationships, and production workflows
  • Unauthorized manipulation of collaboration whiteboards, including creation, modification, or deletion of whiteboard content
  • Creation of bogus or misleading company records that may pollute business data and reporting
  • Facilitation of competitive intelligence gathering or fraud by external parties
  • Erosion of data integrity and trust in the system's records

General mitigation guidance

Effective mitigation typically focuses on enforcing strong authentication and centralizing access control for all sensitive operations.

Common defensive patterns include:

  • Applying a consistent authentication middleware or filter to all API routes handling sensitive business objects (e.g., companies, quotes, orders, tasks, whiteboards)
  • Adopting a secure-by-default routing strategy where all endpoints require authentication unless explicitly designated as public
  • Implementing role- and permission-based access checks on top of authentication for operations that read or modify business-critical data
  • Normalizing authentication logic in a shared component rather than duplicating checks within individual controllers
  • Restricting network exposure of administrative or operational APIs through firewalls, reverse proxies, or API gateways
  • Logging and monitoring access to sensitive endpoints to detect anomalous usage patterns and support incident response

How teams detect issues like this

Organizations can detect this class of issue through a combination of architectural review and automated analysis:

  • Reviewing route and controller configurations to ensure all sensitive endpoints are protected by a common authentication middleware or equivalent mechanism
  • Using static analysis or configuration analysis tools to flag handlers that bypass or do not register authentication filters
  • Implementing automated tests or API contract tests that verify unauthorized requests are rejected with appropriate status codes for every sensitive endpoint
  • Conducting periodic penetration tests and API security assessments focusing on enumeration of unauthenticated endpoints and access to business objects
  • Employing API gateways or service meshes with policy enforcement that can surface calls to endpoints lacking authentication constraints

Sources

SourceLink
github.comgithub.com/SMEWebify/WebErpMesv2/commit/3a7ab1c95d1d1c8f7c62c84bc87b3666ecd2fa23
github.comgithub.com/SMEWebify/WebErpMesv2/security/advisories/GHSA-pp68-5pc2-hv7w

Frequently asked

questions

Yes. As long as the WebErpMesV2 API is reachable over the network (e.g., internet-facing or on a shared internal network), an attacker can send unauthenticated HTTP requests to the exposed endpoints.

No. The core issue is that selected sensitive endpoints do not require authentication at all, so an attacker can interact with them without any credentials.

The most robust pattern is to enforce authentication by default on all API endpoints that handle sensitive or business-critical data, using a centralized middleware or gateway-based control, and then add fine-grained authorization checks for specific operations.

Adopt a secure-by-design API strategy: make authentication mandatory for all non-public endpoints, define explicit criteria for what may be public, enforce those rules in shared infrastructure, and add automated tests and code checks that fail builds when new sensitive routes are introduced without proper authentication and authorization.

Find out what's already
exploitable in your codebase.