CVE-2025-3382
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 has been found in joey-zhou xiaozhi-esp32-server-java up to a14fe8115842ee42ab5c7a51706b8a85db5200b7 and classified as critical. This vulnerability affects the function update of the file /api/user/update. The manipulation of the argument state leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for 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 confidenceSQL injection vulnerability in the /api/user/update API endpoint of xiaozhi-esp32-server-java. The 'state' parameter is directly concatenated into a SQL query without sanitization or parameterized queries, allowing remote attackers to manipulate SQL queries and potentially extract, modify, or delete database contents.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 xiaozhi-esp32-server-java is runningCheck running processes or services for the xiaozhi-esp32-server-java application, or look for its deployment directory on the serverAffected if The application is installed and running on the system
-
Locate the /api/user/update endpoint handlerExamine the application's source code or web server configuration to find the file containing the /api/user/update endpoint implementation, typically in a controller or API handler fileAffected if The endpoint exists and is accessible in the codebase
-
Verify the 'state' parameter is used in the update operationSearch the endpoint handler code for references to 'state' parameter and examine how it is processed before being used in database operationsAffected if The 'state' parameter is accepted and used in the user update logic
-
Check for unsafe SQL query constructionExamine the database query code that uses the 'state' parameter to determine if it uses direct string concatenation or parameterized queries (prepared statements)Affected if The 'state' parameter is directly concatenated into SQL queries without using parameterized queries or input sanitization
-
Confirm database connectivity and accessibilityVerify the application has an active database connection and that the user update functionality can be triggered through the APIAffected if The database is connected and the update endpoint is reachable over the network
If xiaozhi-esp32-server-java is running with the /api/user/update endpoint that directly concatenates the 'state' parameter into SQL queries, 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 dataReplace dynamic SQL construction with parameterized queries/prepared statements for the state parameter, and implement proper input validation on all user-supplied data before database operations.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3382 — 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-3382 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