dbcve.org
MoneyprinterturboApplication · Harry0703

CVE-2025-7896

HIGH · 7.5 CVSS v3.1 Published 2025-07-20
Fix available
A fix is available. Upgrade to after 1.2.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 vulnerability has been found in harry0703 MoneyPrinterTurbo up to 1.2.6 and classified as critical. Affected by this vulnerability is the function download_video/delete_video of the file app/controllers/v1/video.py. The manipulation leads to path traversal. The attack can be launched remotely.

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 confidence

Path traversal vulnerability in MoneyPrinterTurbo's video download/delete functions in app/controllers/v1/video.py allows remote attackers to access or delete arbitrary files on the server by manipulating file path parameters with directory traversal sequences.

MitigationUpdate to version 1.2.7 or later which should contain the fix; alternatively, implement strict input validation on file path parameters to reject traversal sequences like '../' and enforce allowed directory boundaries.

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
MoneyprinterturboApplication
Affected:<= 1.2.6

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 MoneyPrinterTurbo installation and version
    Check the installed version by looking at version tags (git tag), requirements.txt, setup.py, or a version.py file in the project root. Run: git tag | sort -V to list version tags, or grep -r 'version' requirements.txt setup.py 2>/dev/null
    Affected if The installed version is 1.2.6 or lower (any version <= 1.2.6)
  2. Locate the vulnerable video controller file
    Find app/controllers/v1/video.py in the MoneyPrinterTurbo installation directory. Verify the file exists and contains video download/delete endpoint handlers.
    Affected if The file app/controllers/v1/video.py exists and handles video download or delete operations
  3. Check if video download/delete endpoints are network-accessible
    Examine the application's routing configuration (check app/__init__.py, main.py, or any router/blueprint definitions) to confirm the video.py endpoints are registered and exposed via HTTP. Verify if the application binds to a network interface (0.0.0.0) rather than localhost only.
    Affected if The video download/delete endpoints are exposed over the network (accessible via non-localhost interface)
  4. Inspect input validation on file path parameters
    Examine the video.py file for path traversal protection. Look for validation logic that sanitizes or rejects '../' sequences, checks that paths stay within allowed directories, or uses os.path.realpath() to resolve and verify paths.
    Affected if The code lacks proper input validation on file path parameters (no check for '../' or directory boundary enforcement)
  5. Verify if the application uses the vulnerable path-handling code
    Search the video.py file for functions that accept file path parameters (look for parameters named 'path', 'filename', 'file_path', or similar) and directly use them in file operations (open(), os.remove(), send_file()) without validation.
    Affected if The video download/delete functions accept file path parameters and use them directly in file operations without sanitization

You are affected if MoneyPrinterTurbo version 1.2.6 or lower is installed, the video.py controller is exposed via network, and file path parameters in download/delete endpoints lack input validation against directory traversal sequences.

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.

From vendor data
Upgrade available Upgrade to a release after 1.2.6
Interim mitigation

Update to version 1.2.7 or later which should contain the fix; alternatively, implement strict input validation on file path parameters to reject traversal sequences like '../' and enforce allowed directory boundaries.

Fix this in Moneyprinterturbo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7896 — 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-7896 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