dbcve.org
MoneyprinterturboApplication · Harry0703

CVE-2025-7897

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-20
Fix available
A fix is available. Upgrade to after 1.2.6 or later.
See remediation →
100/100
Remediation priority · Urgent
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 was found in harry0703 MoneyPrinterTurbo up to 1.2.6 and classified as critical. Affected by this issue is the function verify_token of the file app/controllers/base.py of the component API Endpoint. The manipulation leads to missing authentication. The attack may 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

The verify_token function in app/controllers/base.py of MoneyPrinterTurbo up to v1.2.6 lacks proper authentication validation, allowing remote attackers to bypass authentication entirely and access protected API endpoints without providing valid credentials.

MitigationUpgrade to version 1.2.7 or later which implements proper token verification in the verify_token function, and ensure all API endpoints enforce authentication checks before processing requests.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MoneyPrinterTurbo installation
    Locate the application directory (e.g., MoneyPrinterTurbo, moneyprinterturbo) or running process that matches the project. Look for app/controllers/base.py file in the codebase.
    Affected if The application is present but you cannot confirm the version is above 1.2.7
  2. Determine installed version
    Check the version by examining version files (version.py, __init__.py, pyproject.toml), git tags (git tag), or the application's startup output. Look for version 1.2.6 or earlier.
    Affected if The installed version is 1.2.6 or any version <= 1.2.6
  3. Inspect verify_token function in app/controllers/base.py
    Open app/controllers/base.py and locate the verify_token function. Examine whether it performs actual token validation (e.g., checks token against a database, validates signature, returns proper True/False).
    Affected if The verify_token function exists but returns True or performs no real authentication validation (empty implementation, always-true condition, or missing validation logic)
  4. Verify API endpoint protection
    Review the API endpoint definitions in the codebase to check if they call verify_token before processing requests. Test accessing a protected endpoint without providing credentials.
    Affected if Protected API endpoints can be accessed without valid authentication tokens

You are affected if MoneyPrinterTurbo version is 1.2.6 or earlier and the verify_token function in app/controllers/base.py lacks proper authentication validation.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.6
Interim mitigation

Upgrade to version 1.2.7 or later which implements proper token verification in the verify_token function, and ensure all API endpoints enforce authentication checks before processing requests.

Recommended fix Moderate confidence

Latest version newer than 1.2.6 (check official repository for exact version)

  1. 1. Check the official harry0703 MoneyPrinterTurbo repository for the latest available release
  2. 2. Download or clone the repository at a version newer than 1.2.6
  3. 3. Review the release notes or changelog to confirm the authentication vulnerability in verify_token is addressed
  4. 4. Backup your current configuration and data
  5. 5. Replace the application files with the new version
  6. 6. Restart the application service
  7. 7. Verify that authentication is now required for the affected API endpoint by attempting an unauthenticated request
Caveat Review release notes for potential configuration or API changes between your version and the new version

Generated from the published advisory — verify against the referenced sources before acting.

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

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 locally
dbcve dependency scanner

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