CVE-2025-70982
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 · uneditedIncorrect access control in the importUser function of SpringBlade v4.5.0 allows attackers with low-level privileges to arbitrarily import sensitive user data.
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 authorization bypass vulnerability in SpringBlade v4.5.0 where the importUser function fails to properly validate user permissions before allowing sensitive user data imports. Attackers with low-level privileges can exploit this to import arbitrary sensitive user data, indicating a missing or insufficient role-based access control (RBAC) check in the import functionality.
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.5.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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Verify SpringBlade versionCheck the installed SpringBlade version by inspecting the project's pom.xml file, application properties, or by querying the application's version endpoint if available. Common locations: src/main/resources/application.yml or the deployed WAR/JAR file metadata.Affected if The installed version is exactly 4.5.0
-
Identify importUser function endpointLocate the importUser function in the codebase. Search for controller classes handling user import functionality. Common paths may include packages like org.springblade.*.controller or similar. Look for methods named importUser, importUsers, or bulkUserImport.Affected if The importUser function exists in the deployed application code
-
Check RBAC configuration for import endpointInspect the security configuration or controller annotations for the importUser endpoint. Look for @PreAuthorize annotations, role definitions, or security filter chains that govern access to this function. Check if there are role requirements like @PreAuthorize("hasRole('ADMIN')") or equivalent.Affected if No role-based authorization check exists, or the check permits low-privilege users (non-admin roles) to access the importUser function
-
Test low-privilege user accessIf you have a test environment, authenticate with a low-privilege user account (e.g., a standard user with minimal permissions) and attempt to access the user import endpoint. Observe whether the request is allowed or rejected.Affected if A low-privilege user can successfully call the importUser endpoint and trigger the sensitive data import operation
Your environment is affected if you are running SpringBlade version 4.5.0 AND the importUser endpoint is accessible without proper admin-level role verification.
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 authorization checks in the importUser function to verify that only users with appropriate high-level privileges (e.g., administrator roles) can import sensitive user data, and validate all input parameters before processing.
- 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-70982 — 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-70982 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