CVE-2025-11607
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 weakness has been identified in harry0703 MoneyPrinterTurbo up to 1.2.6. The impacted element is the function upload_music of the file app/controllers/v1/music.py of the component API Endpoint. Executing a manipulation of the argument File can lead to path traversal. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.
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 confidenceA path traversal vulnerability exists in the upload_music function of MoneyPrinterTurbo v1.2.6 and prior. Remote attackers can manipulate the File argument to write files to arbitrary locations on the server by using directory traversal sequences (e.g., ../../../') in the filename.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate MoneyPrinterTurbo installationSearch for the project directory (commonly named 'MoneyPrinterTurbo' or 'moneyprinterturbo') on the server, typically cloned from GitHub at /opt, /home, or within web server document roots.Affected if The application is found on the system and is accessible via web or local execution.
-
Identify installed versionCheck the version by examining version files (version.py, __version__, requirements.txt, setup.py, or pyproject.toml in the project root), or run 'git tag' if it's a git repository to list all tags.Affected if The version is 1.2.6 or any version lower (e.g., 1.2.5, 1.2.0, etc.).
-
Verify upload_music endpoint exists and is accessibleLocate the source file containing the upload_music function (typically in a web/routes or api module). Check if the function is registered as an API endpoint (routes, app.add_route, or @app.route decorators).Affected if The upload_music function is exposed as a web endpoint and accepts user-supplied filenames.
-
Audit upload directory for unexpected filesExamine the configured upload directory (commonly 'uploads/', 'static/uploads/', or 'storage/music/'). Search for files with traversal patterns in their names (files starting with ../ or containing unusual path separators) and check parent directories for any files written outside the intended upload folder.Affected if Files exist outside the expected upload directory, or files with directory traversal patterns are present in or outside the upload folder.
You are affected if MoneyPrinterTurbo is running and the installed version is 1.2.6 or lower, with the upload_music endpoint exposed and accessible.
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 on filenames to reject directory traversal sequences, normalize and validate the upload path, restrict uploads to an explicit safe directory, and upgrade to the latest version if a patch is available.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11607 — 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-11607 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