CVE-2025-10384
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 · uneditedA flaw has been found in yangzongzhuan RuoYi up to 4.8.1. Affected by this vulnerability is an unknown functionality of the file /system/role/authUser/cancelAll of the component Role Handler. Executing manipulation of the argument roleId/userIds can lead to improper authorization. The attack may be performed from remote. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceThis is an improper authorization vulnerability in the yangzongzhuan RuoYi admin framework (versions up to 4.8.1). The /system/role/authUser/cancelAll endpoint that handles removal of user role assignments fails to properly validate user permissions before allowing manipulation of the roleId/userIds parameters, potentially allowing authenticated users to modify role associations they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.8.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RuoYi framework versionLocate the version identifier in the application's build configuration, pom.xml file, or version manifest typically found in the WEB-INF or root directory of the deployed applicationAffected if The identified version is 4.8.1 or any version lower than 4.8.1
-
Verify the vulnerable endpoint existsCheck if the /system/role/authUser/cancelAll endpoint is present in the deployed application's routing configuration or API documentationAffected if The endpoint is exposed and accessible in the application
-
Examine role authorization configurationReview the security configuration files and the controller implementation for /system/role/authUser/cancelAll to determine whether role-based permission checks are performed before processing role removal requestsAffected if The endpoint lacks proper authorization validation for the roleId and userIds parameters, allowing manipulation by unauthorized authenticated users
-
Review role assignment permission boundariesInspect the database or role management module to determine which roles the current authenticated user is permitted to modify, and compare against what the vulnerable endpoint would allowAffected if The endpoint permits modification of role associations outside the requesting user's authorized scope
A user is affected if the deployed RuoYi version is 4.8.1 or lower and the /system/role/authUser/cancelAll endpoint is accessible without proper authorization validation for the roleId and userIds parameters.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a patched version of RuoYi beyond 4.8.1. If no patched version is available, implement proper role-based access control (RBAC) validation checks on the affected endpoint to verify the requesting user has appropriate permissions before allowing role assignment modifications.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10384 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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