CVE-2025-5522
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 found in jack0240 魏 bskms 蓝天幼儿园管理系统 up to dffe6640b5b54d8e29da6f060e0493fea74b3fad. It has been rated as critical. Affected by this issue is some unknown functionality of the file /sa/addUser of the component User Creation Handler. The manipulation leads to improper authorization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.
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 confidenceImproper authorization vulnerability in the /sa/addUser endpoint of the 蓝天幼儿园管理系统 (Blue Sky Kindergarten Management System). The user creation handler lacks proper authorization checks, allowing unauthenticated or unauthorized remote attackers to create user accounts, potentially with administrative privileges.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the Blue Sky Kindergarten Management System is deployedLocate the web application server hosting the 蓝天幼儿园管理系统 and note its base URL. Check running processes or web server logs for references to '蓝天幼儿园' or 'Blue Sky Kindergarten'.Affected if The system is running and accessible on the network
-
Confirm the /sa/addUser endpoint existsAccess the application's web interface and navigate to or send a request to the /sa/addUser path (e.g., GET https://<host>/sa/addUser or POST to the same endpoint). Observe if the endpoint responds or returns any user creation form.Affected if The endpoint responds (returns any HTTP status other than 404) indicating the vulnerable endpoint is present
-
Test if authentication is required for user creationSend a POST request to /sa/addUser with a test payload (e.g., username=testuser&password=testpass) WITHOUT including any session cookies, authentication tokens, or credentials. Observe the HTTP response.Affected if The request succeeds and returns a success message or creates a user without requiring any authentication credentials
-
Verify if admin privileges can be obtainedIf user creation succeeds, examine whether the created account has elevated privileges or check if the addUser endpoint accepts a role/privilege parameter (such as isAdmin, role, or level) that can grant administrative access.Affected if The endpoint accepts parameters that allow creating accounts with administrative or elevated privileges without authorization checks
-
Check application logs for unauthorized user creation attemptsReview application logs, access logs, or audit trails for entries indicating user creation events from unexpected IP addresses or unauthenticated sessions.Affected if Logs show user creation events originating from unauthenticated requests or unknown sources
If the /sa/addUser endpoint is accessible and allows creating user accounts (especially administrative ones) without requiring valid authentication credentials, the environment is affected by this vulnerability.
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 role-based authorization checks on the /sa/addUser endpoint to verify the requesting user has appropriate permissions before allowing user creation. Apply authentication requirements if not already present.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5522 — 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-5522 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