CVE-2025-5894
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 · uneditedSmart Parking Management System from Honding Technology has a Missing Authorization vulnerability, allowing remote attackers with regular privileges to access a specific functionality to create administrator accounts, and subsequently log into the system using those accounts.
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 confidenceSmart Parking Management System from Honding Technology contains a missing authorization vulnerability that allows authenticated regular users to access administrative functionality for creating new administrator accounts. This enables privilege escalation where a standard user can create an admin account and gain full system access.
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
- 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 Smart Parking Management System installationSearch for files or directories related to Honding Technology Smart Parking Management System. Check web server logs, application directories, or installed software listings for 'Smart Parking' or 'Honding' components.Affected if The Smart Parking Management System from Honding Technology is present in the environment
-
Locate the account creation endpointReview application source code, API routes, or web application structure for account/user creation functionality. Common paths include /admin/user/create, /user/add, /api/users/new, or similar admin-oriented endpoints.Affected if The application contains an account/user creation endpoint accessible within the system
-
Verify authorization enforcement on account creationInspect the code or configuration handling the account creation endpoint. Look for role-based access control (RBAC) checks that verify the requesting user has administrative privileges before allowing account creation.Affected if No role verification or privilege check exists before allowing account creation, or regular authenticated users can trigger the account creation functionality
-
Test regular user access to admin account creationLog in as a non-administrative (regular) user account and attempt to access or invoke the account creation functionality. Observe whether the system allows or rejects the request based on user role.Affected if A regular authenticated user can successfully access or execute the account creation function and create new accounts
-
Check for admin account creation capability for regular usersUsing a regular user session, attempt to create an account with administrative privileges or elevated permissions. Verify whether the system permits creation of admin-level accounts without proper authorization.Affected if Regular users can create administrator-level accounts in the system
The environment is affected if the Smart Parking Management System from Honding Technology is installed and regular authenticated users can access or trigger the account creation endpoint without proper admin privilege 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 role-based access control (RBAC) to enforce authorization checks on administrative functions, ensuring only users with administrator privileges can access account creation endpoints. Validate user permissions before executing any privileged operation.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5894 — 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-5894 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