CVE-2025-49089
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 · uneditedwangxutech MoneyPrinterTurbo 1.2.6 allows path traversal via /api/v1/download/ URIs such as /api/v1/download//etc/passwd.
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 confidenceMoneyPrinterTurbo 1.2.6 contains a path traversal vulnerability in the /api/v1/download/ endpoint. By supplying URIs with directory traversal sequences (e.g., /api/v1/download//etc/passwd), an attacker can read arbitrary files on the host system outside the intended download directory.
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= 1.2.6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm MoneyPrinterTurbo is installedLocate the MoneyPrinterTurbo application installation directory or running process. This may be found via process monitoring, service listings, or common installation paths for Python web applications.Affected if The application is present and running on the system
-
Check the installed versionExamine the application's version information. This may be in a VERSION file, setup.py, pyproject.toml, or displayed in the application startup logs. Compare the version number to 1.2.6.Affected if The installed version is exactly 1.2.6
-
Verify the download API endpoint is exposedCheck if the web application is running and the /api/v1/download/ endpoint is accessible. This may require checking the application's routing configuration or attempting to access the endpoint if the service is externally reachable.Affected if The /api/v1/download/ endpoint is accessible and responds to requests
-
Identify if directory traversal protection is absentReview the application's configuration and code for the download endpoint. Look for input validation or path sanitization logic on file path parameters. In a default installation of version 1.2.6, such validation is absent.Affected if The application lacks input validation on the file path parameter in the download endpoint, allowing ../ sequences to be processed
A user is affected if MoneyPrinterTurbo version 1.2.6 is installed and running with the /api/v1/download/ endpoint accessible without proper path traversal protection.
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 strict input validation and canonicalization on file path parameters in the download API endpoint. Sanitize or reject requests containing '../' sequences and restrict downloads to an allowed base directory.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49089 — 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-49089 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