dbcve.org
MinervaApplication · Agilonhealth

CVE-2026-5781

HIGH · 8.8 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An authorization vulnerability in MphRx's Minerva V3.6.0, specifically in the '/minerva/moUser/update' endpoint, could allow an authenticated user with user modification privileges to escalate their privileges by sending an HTTP request with a manipulated 'identifier' field. Successful exploitation of this vulnerability could allow an authenticated user to obtain administrator privileges. It is not possible to escalate privileges through the graphical user interface.

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

MphRx Minerva v3.6.0 contains an insecure direct object reference (IDOR) or broken access control vulnerability in the /minerva/moUser/update endpoint. An authenticated attacker with standard user modification privileges can manipulate the 'identifier' field in an HTTP request to escalate their own account or other user accounts to administrator level. The GUI enforces proper authorization but the API endpoint does not perform equivalent server-side validation.

MitigationImplement robust server-side authorization checks on all API endpoints that validate the requesting user's permissions against the requested action and target resource. Apply the principle of least privilege to user modification features and audit the entire API surface for similar authorization bypasses.

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
MinervaApplication
Affected:= 3.6.0

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

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

  1. Verify Minerva version
    Check the installed Minerva version by reviewing application logs, build metadata, or the /minerva/version endpoint if available. Compare against the affected version 3.6.0.
    Affected if The installed version is exactly 3.6.0.
  2. Confirm endpoint exposure
    Verify the /minerva/moUser/update endpoint is accessible in the environment by checking web server configuration, URL allowlists, or network exposure settings.
    Affected if The /minerva/moUser/update endpoint is accessible and responds to HTTP requests.
  3. Check user modification feature
    Determine if user modification or profile update features are enabled for non-admin users. Review application configuration for user management module settings.
    Affected if The user modification feature is enabled and users with standard modification privileges can access profile update functions.
  4. Inspect authorization controls
    Review application logs or perform a controlled test (if authorized) to check whether the /minerva/moUser/update endpoint validates that the authenticated user can only modify their own record by examining the identifier parameter. Check server-side code or API security policies for proper ownership validation.
    Affected if The endpoint does not validate that the requesting user owns the identifier being modified, allowing privilege escalation.

A user is affected if they have Minerva version 3.6.0 installed, the /minerva/moUser/update endpoint is accessible, user modification is enabled, and the endpoint lacks proper authorization checks on the identifier parameter.

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

Implement robust server-side authorization checks on all API endpoints that validate the requesting user's permissions against the requested action and target resource. Apply the principle of least privilege to user modification features and audit the entire API surface for similar authorization bypasses.

Fix this in Minerva Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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