CVE-2025-46174
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 · uneditedRuoyi v4.8.0 vulnerable to Incorrect Access Control. There is a missing checkUserDataScope permission check in the resetPwd Method of SysUserController.java.
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 · high confidenceRuoYi v4.8.0 contains an Incorrect Access Control vulnerability in SysUserController.java where the resetPwd method is missing a checkUserDataScope permission verification. This allows authenticated users to potentially reset passwords for accounts outside their authorized data scope, bypassing the intended permission boundaries.
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.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm RuoYi versionLocate the RuoYi application version file or build configuration. Check for version 4.8.0 specifically. This may be in a pom.xml, version.properties, or the application startup logs.Affected if The installed RuoYi version is exactly 4.8.0
-
Locate SysUserController.javaFind the SysUserController.java file in the application source code or decompiled bytecode. This is typically in a controller or web package related to user management.Affected if The file exists and contains a resetPwd method implementation
-
Inspect resetPwd method for permission checkOpen SysUserController.java and locate the resetPwd method. Examine whether the method includes a call to checkUserDataScope or any data scope permission validation before performing the password reset operation.Affected if The resetPwd method exists but does NOT contain checkUserDataScope or equivalent permission validation logic
-
Verify data scope configurationCheck if the application has data scope permissions configured and enforced for other user-related operations. Confirm that checkUserDataScope is used in other similar methods within the same controller.Affected if Data scope checks are implemented elsewhere but are missing from resetPwd, indicating an incomplete implementation
-
Test password reset boundaryUsing an authenticated user with limited data scope, attempt to reset the password of a user outside their authorized scope. If successful without error, the vulnerability is present.Affected if An authenticated user can reset passwords for accounts outside their defined data scope
The environment is affected if running RuoYi version 4.8.0 and the resetPwd method in SysUserController.java lacks the checkUserDataScope permission verification that other similar methods include.
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 dataAdd the missing checkUserDataScope permission check to the resetPwd method to enforce proper authorization before allowing password resets.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46174 — 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-46174 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