dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-55585

CRITICAL · 9.0 CVSS v4.0 Published 2025-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/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
In the moPS App through 1.8.618, all users can access administrative API endpoints without additional authentication, resulting in unrestricted read and write access, as demonstrated by /api/v1/users/resetpassword.

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 moPS App through version 1.8.618 contains a broken access control vulnerability where authentication controls fail to enforce proper authorization on administrative API endpoints. Any authenticated user can directly access privileged endpoints like /api/v1/users/resetpassword without elevated privileges, allowing complete administrative read/write access.

MitigationImplement role-based access control (RBAC) with proper authorization checks on all administrative API endpoints, requiring admin-level authentication before allowing access to sensitive operations like password resets.

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
Authentication
None
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:N/R:X/V:X/RE:M/U:Red

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 moPS App version
    Locate the moPS App version information in the application settings, about page, or version file. Common locations include the application header, footer, or admin panel 'About' section. Compare the version number to the affected range (1.8.618 and below).
    Affected if The installed version is 1.8.618 or lower.
  2. Verify API endpoint accessibility
    Send a direct HTTP request to the administrative API endpoint /api/v1/users/resetpassword using a web proxy or curl command, without providing any authentication credentials or with a standard non-privileged user account.
    Affected if The endpoint returns successful data or a 2xx status code instead of requiring elevated privileges or returning 401/403.
  3. Confirm lack of authorization enforcement
    Attempt to perform a sensitive administrative operation through the API (such as password reset for another user) using an account that should not have admin privileges. Inspect the HTTP response for success indicators.
    Affected if The operation completes successfully, indicating no role-based access control is enforced on the admin endpoint.

You are affected if the moPS App version is 1.8.618 or lower AND the admin API endpoint /api/v1/users/resetpassword is accessible without proper admin authentication.

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

Implement role-based access control (RBAC) with proper authorization checks on all administrative API endpoints, requiring admin-level authentication before allowing access to sensitive operations like password resets.

Recommended fix Moderate confidence

Latest available version of moPS App (any version higher than 1.8.618)

  1. 1. Identify the current installed version of moPS App by checking the application settings or about page
  2. 2. Navigate to the official moPS application download page or repository
  3. 3. Download and install the latest available version of moPS App (version higher than 1.8.618)
  4. 4. Verify the installation was successful and confirm the new version number
  5. 5. Test the /api/v1/users/resetpassword endpoint to confirm authentication is now required

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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