CVE-2025-13806
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 security vulnerability has been detected in nutzam NutzBoot up to 2.6.0-SNAPSHOT. This impacts an unknown function of the file nutzboot-demo/nutzboot-demo-simple/nutzboot-demo-simple-web3j/src/main/java/io/nutz/demo/simple/module/EthModule.java of the component Transaction API. The manipulation of the argument from/to/wei leads to improper authorization. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.
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 confidenceVulnerability in NutzBoot's EthModule.java Transaction API where manipulation of from/to/wei arguments leads to improper authorization. The issue affects the Ethereum-related transaction handling in the demo application, allowing unauthorized transactions to be processed. Public exploit available indicates ease of exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.6.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 NutzBoot installation and versionLocate the NutzBoot libraries or dependencies in your project (check pom.xml, lib folder, or build configuration). Determine the installed version number.Affected if The installed NutzBoot version is 2.6.0 or lower.
-
Locate EthModule.java in the codebaseSearch for the file EthModule.java in your source code or compiled classes. This file contains the Transaction API with the vulnerable from/to/wei parameter handling.Affected if EthModule.java with Transaction API handling Ethereum parameters is present in the application.
-
Verify Ethereum transaction endpoints are exposedCheck application routing/configuration for endpoints handled by EthModule (typically /eth/ or similar paths related to Ethereum transactions). Identify if from/to/wei parameters are accepted via API calls.Affected if Transaction API endpoints accepting from/to/wei parameters are publicly accessible or unauthenticated.
-
Confirm demo application deploymentDetermine if the deployed application is the NutzBoot demo application or includes demo functionality for Ethereum transactions.Affected if The demo application with Ethereum transaction handling is deployed.
-
Check for missing authorization on Transaction APIReview the EthModule.java code or intercept API requests to verify whether authorization checks occur before processing from/to/wei transaction parameters.Affected if No authorization validation is performed before processing from/to/wei arguments in Transaction API calls.
You are affected if NutzBoot version is 2.6.0 or lower AND the EthModule Transaction API with Ethereum from/to/wei parameters is exposed without proper authorization checks.
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 proper authorization checks on all Transaction API endpoints, validate caller permissions before processing from/to/wei parameters, and restrict transaction operations to authorized users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13806 — 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-13806 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