dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-39901

MEDIUM · 5.7 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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
monetr is a budgeting application focused on planning for recurring expenses. Prior to 1.12.3, a transaction integrity flaw allows an authenticated tenant user to soft-delete synced non-manual transactions through the transaction update endpoint, despite the application explicitly blocking deletion of those transactions via the normal DELETE path. This bypass undermines the intended protection for imported transaction records and allows protected transactions to be hidden from normal views. This vulnerability is fixed in 1.12.3.

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

In monetr prior to 1.12.3, the transaction update endpoint lacks proper authorization checks that exist on the DELETE endpoint. An authenticated tenant user can soft-delete synced non-manual (imported) transactions by sending an update request with a deletion flag, bypassing the explicit protection blocking deletion through the normal DELETE path. This allows imported transaction records to be hidden from views while remaining in the database.

MitigationUpgrade to monetr version 1.12.3 or later, which adds proper authorization checks to the transaction update endpoint to match the protection already present on the DELETE endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/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 installed monetr version
    Check the running container, binary, or application startup logs for the version string. Common locations: container image tag, Helm chart values, docker-compose.yml version field, or the application UI footer if version is displayed there.
    Affected if The installed version is lower than 1.12.3 (e.g., 1.12.2, 1.11.0, etc.)
  2. Verify transaction update endpoint behavior
    As an authenticated tenant user, attempt a PATCH or PUT request to the transaction update endpoint (typically /api/transactions/:id or similar) with a soft-delete indicator such as 'deleted: true', 'isDeleted: true', or similar field in the request body. Observe whether the operation succeeds on a synced non-manual transaction.
    Affected if The update request successfully soft-deletes a synced non-manual transaction that was imported, bypassing the deletion protections that the DELETE endpoint enforces.
  3. Confirm presence of synced non-manual transactions
    Query the transactions database table or API to identify records that have isManual set to false and contain sync-related metadata (such as a bank account link, sync ID, or external reference ID).
    Affected if The system contains imported transactions with sync identifiers; without such records, the vulnerability has no practical impact in this environment.
  4. Check authentication and authorization settings
    Review the API configuration and authentication logs to confirm that tenant users have access to the transaction update endpoint. The flaw requires an authenticated user with transaction update permissions.
    Affected if Authenticated tenant users can access the transaction update endpoint and modify transaction records.

You are affected if your monetr installation is version 1.12.3 or earlier, you have synced non-manual transactions in the system, and authenticated users can successfully soft-delete those transactions through the update endpoint despite such operations being blocked on the delete path.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to monetr version 1.12.3 or later, which adds proper authorization checks to the transaction update endpoint to match the protection already present on the DELETE endpoint.

Recommended fix High confidence

1.12.3

  1. 1. Check the current version of monetr being running (e.g., via docker tag, application UI, or CLI)
  2. 2. Backup the monetr database and configuration files before proceeding
  3. 3. Upgrade to version 1.12.3 or later (e.g., docker pull monetr/monetr:1.12.3 or update deployment manifests)
  4. 4. Restart the monetr application service
  5. 5. Verify the upgrade was successful by checking the application version
  6. 6. Log in as an authenticated tenant user and confirm the transaction update endpoint no longer allows soft-deleting synced non-manual transactions
Caveat None mentioned in the advisory

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

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