CVE-2025-7895
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, which was classified as critical, was found in harry0703 MoneyPrinterTurbo up to 1.2.6. Affected is the function upload_bgm_file of the file app/controllers/v1/video.py of the component File Extension Handler. The manipulation of the argument File leads to unrestricted upload. It is possible to launch the attack 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 confidenceMoneyPrinterTurbo up to v1.2.6 contains an unrestricted file upload vulnerability in the upload_bgm_file function within app/controllers/v1/video.py. The component fails to validate file extensions or content types before storing uploaded files, allowing remote attackers to upload malicious executable files (e.g., web shells) that could lead to remote code execution.
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
- 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.
-
Confirm MoneyPrinterTurbo is installedLocate the application directory - typically installed via 'git clone https://github.com/Harry0703/MoneyPrinterTurbo' or pip. Look for the project directory containing app/controllers/v1/video.pyAffected if The application directory exists on the system
-
Identify the installed versionCheck the version file or git tags: run 'git tag' in the project directory, or look for version indicators in setup.py, pyproject.toml, or the main application fileAffected if The version is 1.2.6 or lower (or no version file is found, indicating an older installation)
-
Verify the vulnerable function existsExamine app/controllers/v1/video.py and locate the 'upload_bgm_file' function definition. Check if it performs any file extension or MIME type validation before saving uploaded filesAffected if The function exists and contains no file extension/content-type validation checks (e.g., no allowlist, no os.path.splitext validation, no mimetype checking)
-
Check if the web interface is exposedVerify the application runs as a web service (Flask/FastAPI). Look at how the application is started (main.py, app.py) and check if binding exposes it to network interfaces (0.0.0.0) rather than localhost onlyAffected if The application is accessible over the network (0.0.0.0 binding or reverse proxy configuration)
-
Inspect the upload directory configurationReview the application configuration to determine where uploaded files are stored. Check if uploads are placed within the webroot (static/ or public/ directories) and whether script execution is disabledAffected if Uploaded files are stored inside the web-accessible directory without restrictions
You are affected if MoneyPrinterTurbo v1.2.6 or lower is running with the upload_bgm_file function accessible over the network and storing uploads in a web-accessible location without extension/content-type validation.
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 allowlist-based file extension and MIME type validation for the upload_bgm_file function, store uploaded files outside the webroot with randomized filenames, and disable script execution permissions on the upload directory.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7895 — 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-7895 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