# CVE-2025-5893: Honding Technology Smart Parking Management System - Exposure of Sensitive Information

> Unauthenticated attackers can access a specific page to obtain plaintext administrator credentials, leading to potential system compromise.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2025
- **Updated:** 9 Jun 2025
- **Also known as:** GHSA-vwm9-6f8w-5whc

## What is CVE-2025-5893?

CVE-2025-5893 is a critical vulnerability in Honding Technology Smart Parking Management System, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Smart Parking Management System from Honding Technology has an Exposure of Sensitive Information vulnerability, allowing unauthenticated remote attackers to access a specific page and obtain plaintext administrator credentials.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2025-5893?


## How do I fix CVE-2025-5893?

No fix has been published for CVE-2025-5893 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5893 being exploited?

There is no known exploitation of CVE-2025-5893 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5893 and fix it if it is affected.

What it is: CVE-2025-5893 is a critical vulnerability in Honding Technology Smart Parking Management System, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5893 in the wild and no public exploit code.

Affected product: Honding Technology Smart Parking Management System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5893/ (Markdown: https://insights.sbomify.com/CVE-2025-5893/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5893
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5893
- OSV: https://osv.dev/vulnerability/CVE-2025-5893

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5893/
Summaries are generated and may contain mistakes; the official description above is the record.