CVE-2025-10988
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 vulnerability was identified in YunaiV ruoyi-vue-pro up to 2025.09. This affects an unknown part of the file /crm/business/transfer. Such manipulation leads to improper authorization. It is possible to launch the attack remotely. The exploit is publicly available and might 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 YunaiV ruoyi-vue-pro affecting the /crm/business/transfer endpoint. The lack of proper authorization checks on this CRM business transfer functionality allows unauthenticated or unauthorized users to access or manipulate transfer operations, leading to unauthorized access to sensitive customer relationship data and business processes.
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<= 2025.09CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the installed version of Ruoyi Vue ProLocate the project version file (typically pom.xml for Maven projects, build.gradle for Gradle, or package.json for frontend) and check the version declaration against the affected range (<=2025.09)Affected if The installed version is 2025.09 or earlier and includes the CRM module
-
Verify if the CRM business module is deployedCheck the deployed application for the presence of the CRM module by inspecting the web application structure, looking for /crm/ endpoints or the business transfer functionality in the deployed WAR/JAR files or frontend bundlesAffected if The CRM module with business transfer functionality is present in the deployment
-
Test authorization on the /crm/business/transfer endpointSend an HTTP request to /crm/business/transfer (using GET or POST) without providing valid authentication credentials or with a low-privilege user account and observe whether the request is accepted or rejectedAffected if The endpoint accepts requests without proper authentication or returns business data without authorization validation
-
Inspect the security configuration for CRM endpointsExamine the Spring Security or equivalent security configuration files (such as SecurityConfig.java) to verify if specific authorization rules exist for /crm/business/transfer endpoints, including any @PreAuthorize annotations or role-based access controlsAffected if No explicit authorization rules or role checks are defined for the transfer endpoint in the security configuration
-
Review the transfer API implementationLocate the controller class handling /crm/business/transfer (typically BusinessTransferController or similar) and inspect the method implementation for @PreAuthorize, @Secured, or method-level permission checksAffected if The transfer operation method lacks proper authorization annotations or permission validation logic
A user is affected if they run Ruoyi Vue Pro version 2025.09 or earlier with the CRM module deployed and the /crm/business/transfer endpoint is accessible without proper authorization validation.
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 dataImplement proper role-based access control (RBAC) and authorization validation on the /crm/business/transfer endpoint. Verify user permissions before allowing any transfer operations, and add authentication checks to ensure only authorized personnel can access this CRM functionality.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10988 — 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-10988 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