dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-15135

MEDIUM · 6.3 CVSS v3.1 Published 2025-12-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A weakness has been identified in joey-zhou xiaozhi-esp32-server-java up to 3.0.0. This impacts the function tryAuthenticateWithCookies of the file AuthenticationInterceptor.java of the component Cookie Handler. Executing manipulation can lead to improper authentication. The attack can be launched remotely. The exploit has been made available to the public and could be exploited. Upgrading to version 4.0.0 will fix this issue. It is recommended to upgrade the affected component.

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 confidence

The vulnerability exists in the tryAuthenticateWithCookies function within the AuthenticationInterceptor.java Cookie Handler component of the xiaozhi-esp32-server-java application. Attackers can manipulate cookies to bypass authentication and gain unauthorized access to protected resources. This affects all versions up to 3.0.0.

MitigationUpgrade the affected component to version 4.0.0. After upgrading, verify that cookie-based authentication functions correctly and that the improper authentication vulnerability is resolved.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if xiaozhi-esp32-server-java is deployed
    Check running Java processes, running services, or application directories for the xiaozhi-esp32-server-java application
    Affected if The application is present in the environment
  2. Determine the installed version
    Check the application version by examining the JAR file name, WAR file, pom.xml, build configuration, or version file. Compare against the affected range (all versions up to 3.0.0)
    Affected if The installed version is 3.0.0 or earlier
  3. Locate the AuthenticationInterceptor component
    Search for AuthenticationInterceptor.java in the deployed application code or libraries, specifically checking for the Cookie Handler functionality within the tryAuthenticateWithCookies function
    Affected if The AuthenticationInterceptor.java with Cookie Handler is present in the deployment
  4. Verify cookie-based authentication is in use
    Check application configuration files, web.xml, or authentication settings to determine if cookie-based authentication is enabled or used
    Affected if Cookie-based authentication is enabled or configured

The environment is affected if xiaozhi-esp32-server-java version 3.0.0 or earlier is deployed with the AuthenticationInterceptor Cookie Handler component and cookie-based authentication is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the affected component to version 4.0.0. After upgrading, verify that cookie-based authentication functions correctly and that the improper authentication vulnerability is resolved.

Recommended fix High confidence

4.0.0

  1. Identify the current version of joey-zhou/xiaozhi-esp32-server-java in use (check pom.xml, build.gradle, or dependency management)
  2. Confirm the version is 3.0.0 or below (vulnerable versions)
  3. Upgrade the dependency to version 4.0.0 (update pom.xml, build.gradle, or equivalent dependency file)
  4. Rebuild and redeploy the application
  5. Verify that the AuthenticationInterceptor.java has been updated to version 4.0.0
Caveat Review the 4.0.0 release notes for any API or configuration changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15135 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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