dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-15752

HIGH · 7.3 CVSS v3.1 Published 2026-07-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in zhinianboke xianyu-auto-reply up to dcb445ad97816ad65299a7580ee0c8c8f929da84. Affected is an unknown function of the file /api/v1/users/ of the component Backend User Endpoint. Performing a manipulation results in missing authorization. The attack may be initiated remotely. The exploit has been made public and could be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The patch is named 19fc3282a1bb78a05c34945c088525d20e081cbd. Applying a patch is the recommended action to fix this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing authorization in the /api/v1/users/ backend endpoint allows unauthenticated or unauthorized remote attackers to access or manipulate user data. The vulnerability exists in the user management API component of the xianyu-auto-reply application.

MitigationApply patch commit 19fc3282a1bb78a05c34945c088525d20e081cbd to implement proper authorization checks on the user endpoint, or upgrade to the latest rolling release that includes the fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify xianyu-auto-reply installation
    Locate the xianyu-auto-reply application in your environment by checking running services, container images, installed packages, or source code directories
    Affected if The xianyu-auto-reply application is present in your environment
  2. Determine application version
    Check the installed version of xianyu-auto-reply using package managers, git tags, docker image tags, or version files in the application directory
    Affected if The version is older than the release containing the fix for commit 19fc3282a1bb78a05c34945c088525d20e081cbd
  3. Verify /api/v1/users/ endpoint exposure
    Examine your web server configuration, API gateway settings, reverse proxy rules, or network access controls to determine if the /api/v1/users/ endpoint is externally or internally accessible
    Affected if The /api/v1/users/ endpoint is exposed and reachable from your network
  4. Test endpoint authorization
    Send an unauthenticated or unauthorized HTTP request to the /api/v1/users/ endpoint and verify whether the application returns user data or allows user manipulation without requiring valid credentials
    Affected if The endpoint returns user data or accepts user modifications without proper authorization

If xianyu-auto-reply is deployed with the /api/v1/users/ endpoint accessible without valid authorization credentials, you are affected by this vulnerability

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Apply patch commit 19fc3282a1bb78a05c34945c088525d20e081cbd to implement proper authorization checks on the user endpoint, or upgrade to the latest rolling release that includes the fix.

Recommended fix Moderate confidence
  1. Clone or navigate to the repository for zhinianboke xianyu-auto-reply
  2. Verify the current HEAD is at or before commit dcb445ad97816ad65299a7580ee0c8c8f929da84
  3. Fetch the latest changes from the remote repository
  4. Apply the fix by cherry-picking or merging commit 19fc3282a1bb78a05c34945c088525d20e081cbd
  5. Review the changes to understand the authorization fix applied to /api/v1/users/ endpoint
  6. Rebuild and redeploy the application
  7. Verify the fix by testing that the Backend User Endpoint now properly enforces authorization checks

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15752 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data