/

CVE-2026-35552

Severity:

HIGH RISK

(8.1)

Missing Authorization (CWE-862) in CAXperts Admin API

CVE-2026-35552

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Privilege Escalation and Service Disruption

Severity:

HIGH RISK

(8.1)

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

CAXperts UPVWebServices and UDiTH Portal contain a missing authorization flaw in an administrative API endpoint that is exposed to authenticated users.

Under certain conditions, a non-privileged remote user can call this endpoint and deactivate the application's license, impacting service availability and administration.

Affected context

The vulnerability appears in deployments of CAXperts UPVWebServices (versions 2.4.2212.603 through 2.7.6) and UDiTH Portal (versions 2026.0.0 through 2026.2.0) where authenticated users can reach backend web service endpoints.

It manifests specifically on an administrative API route responsible for license management that does not enforce role- or permission-based authorization checks.

Environments that expose this endpoint to general authenticated users, such as shared portals or multi-tenant setups, are more likely to be affected.

Exploit preconditions

  • Attack surface: Remote, via HTTP(S) access to the web application's backend API.
  • Required access: Valid authenticated user account with network access to the affected instance.
  • Trigger point: Invoking the administrative license-management endpoint (e.g., deactivate license) without being a privileged or admin user.
  • Why exploitation is possible: The endpoint verifies authentication but omits or misconfigures authorization controls, allowing any logged-in user to perform an administrative operation.

Why this happens

This vulnerability stems from incomplete enforcement of authorization on a sensitive backend operation.

The application correctly requires that users be authenticated to reach the API, but fails to enforce that only privileged roles can execute the license deactivation action.

This aligns with CWE-862: Missing Authorization, where business-critical functions do not perform explicit access control checks, allowing users with insufficient privileges to invoke administrative capabilities.

Potential impact

  • An authenticated user could deactivate the application's license, disrupting service availability.
  • Unauthorized users may gain effective control over license lifecycle and operational status.
  • Administrators might lose control over when and how licenses are deactivated.
  • Repeated abuse could lead to denial of service and operational downtime for dependent teams or customers.

General mitigation guidance

Mitigation typically focuses on enforcing robust authorization around administrative operations and sensitive APIs.

Common defensive patterns include:

  • Applying explicit role- and permission-based checks on all license and configuration management endpoints.
  • Centralizing authorization logic so that administrative routes cannot bypass consistent access control policies.
  • Implementing least-privilege role design, ensuring standard users lack permissions to invoke administrative functions.
  • Using defense-in-depth controls such as segregated admin interfaces, separate authentication realms, or network segmentation for admin APIs.
  • Logging and monitoring access to sensitive endpoints to identify misuse or misconfiguration early.

How teams detect issues like this

Detection efforts can focus on both code-level and operational signals:

  • Static analysis or manual code review to identify controller methods that perform license or configuration changes without checking user roles or permissions.
  • API specification and policy checks (e.g., using OpenAPI and access control linting) to ensure sensitive endpoints are bound to admin roles.
  • Runtime logging and SIEM alerts for unexpected license deactivation events, especially from non-admin accounts or unusual IP ranges.
  • Automated tests or security regression suites that simulate non-privileged users calling administrative endpoints and assert access is denied.

Sources

SourceLink
caxperts.comcaxperts.com
github.comgithub.com/caxperts/security-advisories/blob/main/2026/CAXSEC-2026-001_portal.md

Frequently asked

questions

Yes. Any attacker who can authenticate to the application and reach the affected API over the network may be able to exploit it, assuming no additional compensating controls are in place.

No. The core issue is that the administrative endpoint lacks proper authorization checks, so a standard authenticated account may be sufficient to deactivate the license.

Ensure that all administrative and license-related endpoints enforce strict role-based or permission-based authorization, centralize access control checks, and deny access by default when a user's role is not explicitly allowed.

Adopt a consistent access control framework, require explicit authorization for every sensitive action, validate access rules through code review and automated tests, and treat any new admin or configuration endpoint as requiring additional scrutiny and restricted exposure.

Find out what's already
exploitable in your codebase.