/

CVE-2026-15752

Severity:

HIGH RISK

(7.3)

Missing Backend User AuthZ (CWE-862) in Xianyu API

CVE-2026-15752

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-862, CWE-863

Impact:

Unauthorized Access to User Data and Operations

Severity:

HIGH RISK

(7.3)

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

A missing authorization check in the /api/v1/users/ backend endpoint of xianyu-auto-reply allows unauthorized access to user-related functionality.

When remote callers can reach this API without proper permission validation, they may perform actions or obtain data that should be restricted to authenticated or privileged users.

Affected context

This vulnerability occurs in deployments of the xianyu-auto-reply backend where the /api/v1/users/ endpoint is exposed to remote clients.

It is relevant in environments that rely on this endpoint for user management or retrieval and expect role- or identity-based restrictions.

The issue manifests when the endpoint is reachable over the network and no explicit authorization logic is enforced on incoming requests, even if authentication or roles exist elsewhere in the system.

Exploit preconditions

  • Attack surface: Public or internal HTTP API at /api/v1/users/
  • Required access: Network access to the backend service hosting the user endpoint; no valid account or elevated role appears to be required
  • Trigger point: Sending crafted HTTP requests to the affected user API operations that lack authorization checks
  • Why exploitation is possible: The backend relies on incomplete or missing enforcement of authorization policies (CWE-862/CWE-863), allowing callers to invoke sensitive user operations without verifying their identity or permissions

Why this happens

The root cause lies in missing or incorrect enforcement of access control on the backend user endpoint.

Instead of consistently validating the caller's identity, role, and permissions for operations performed through /api/v1/users/, the implementation either omits authorization checks or applies them in a way that fails to cover all relevant code paths.

This aligns with CWE-862: Missing Authorization and CWE-863: Incorrect Authorization, where security relies on assumptions about trusted callers rather than explicit, centralized policy enforcement.

Potential impact

  • Unauthorized retrieval of user account details
  • Unauthorized modification or deletion of user records
  • Escalation of privileges through manipulation of user roles or attributes
  • Exposure of sensitive user-related metadata that could aid further attacks
  • Violation of privacy requirements or regulatory compliance obligations

General mitigation guidance

Effective mitigation focuses on enforcing robust, consistent authorization checks at the backend layer.

Common defensive patterns include:

  • Centralizing authorization logic and applying it to all user-related endpoints, including /api/v1/users/
  • Enforcing role- and permission-based checks, ensuring that only authenticated and appropriately privileged principals can perform sensitive user operations
  • Designing APIs so that default behavior is deny-by-default, requiring explicit grants for each operation
  • Minimizing the data and operations exposed over user endpoints, following least-privilege and limiting actions to what is strictly necessary
  • Separating public, authenticated, and administrative API surfaces and ensuring each is guarded by the appropriate policy enforcement mechanism

How teams detect issues like this

Detection typically combines code analysis, configuration review, and runtime monitoring:

  • Static analysis rules and manual code review focused on security-sensitive endpoints, checking that every user-related operation invokes a centralized authorization routine
  • Examination of routing and controller logic to verify that authentication and authorization middleware cannot be bypassed on /api/v1/users/
  • Policy-based checks in CI/CD pipelines that flag new endpoints missing explicit access-control annotations or decorators
  • Runtime logging of access attempts to user endpoints and alerting on anomalous patterns, such as unauthenticated access or high-volume requests from unexpected sources

Sources

SourceLink
github.comgithub.com/zhinianboke/xianyu-auto-reply/
github.comgithub.com/zhinianboke/xianyu-auto-reply/commit/19fc3282a1bb78a05c34945c088525d20e081cbd
github.comgithub.com/zhinianboke/xianyu-auto-reply/issues/192
vuldb.comvuldb.com/cve/CVE-2026-15752
vuldb.comvuldb.com/submit/856716
vuldb.comvuldb.com/vuln/378334
vuldb.comvuldb.com/vuln/378334/cti

Frequently asked

questions

It can be, if the /api/v1/users/ endpoint is exposed to the internet or reachable through a network path that untrusted clients can access. The exploit has been disclosed publicly, making opportunistic attacks more likely.

The vulnerability description suggests missing authorization, meaning that network access to the endpoint may be sufficient. In practice, session or token checks should not be assumed to be adequate unless verified in code.

Introduce or enforce a centralized authorization mechanism for all user-related operations, ensure deny-by-default behavior, and require explicit, role-based permission checks on every handler under /api/v1/users/.

Adopt a security design where authentication and authorization are mandatory middleware for all sensitive endpoints, define clear access-control policies for user operations, and enforce them via automated tests, code review guidelines, and static analysis rules during development.

Find out what's already
exploitable in your codebase.