CVE-2024-46624
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 · uneditedAn issue in InfoDom Performa 365 v4.0.1 allows authenticated attackers to elevate their privileges to Administrator via a crafted payload sent to /api/users.
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 confidenceInfoDom Performa 365 v4.0.1 contains an insecure direct object reference or broken access control vulnerability in the /api/users endpoint that allows authenticated users to modify their own privileges or other user accounts to gain Administrator-level access through a crafted API payload.
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
- 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.
-
Identify InfoDom Performa 365 installation and versionLocate the InfoDom Performa 365 installation directory or check the application version through its web interface, configuration files, or installed programs list on the server.Affected if The installed version is InfoDom Performa 365 v4.0.1 or falls within the affected version range.
-
Verify /api/users endpoint is accessibleAttempt to access the /api/users endpoint with a valid authenticated session using a non-administrator user account. This can be done via curl, Postman, or browser developer tools.Affected if The endpoint returns a successful response (HTTP 200) rather than a 403 Forbidden error for an authenticated non-admin user.
-
Test for privilege escalation via API payloadSend a crafted API request to /api/users modifying your own user account or another user's account to set role or privilege level to Administrator. Inspect the request/response.Affected if The API accepts the payload and returns success, allowing a non-admin user to escalate privileges to Administrator.
-
Review user account role assignmentsQuery the user database or /api/users endpoint to list all user accounts and their current role assignments. Look for accounts with Administrator privileges that were not created by an existing Administrator.Affected if There are user accounts with Administrator roles that should not have elevated privileges, indicating successful exploitation.
-
Check application logs for unauthorized accessReview application logs, access logs, or audit logs for requests to /api/users from non-admin accounts, especially those modifying role or privilege fields.Affected if Logs show non-admin users accessing or modifying user role data through the API.
A defender is affected if InfoDom Performa 365 v4.0.1 (or an affected version) is running and the /api/users endpoint allows authenticated non-admin users to modify role assignments and escalate to Administrator privileges.
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 dataApply vendor patch if available; otherwise, implement proper role-based access control (RBAC) validation on the /api/users endpoint to ensure only users with Administrator privileges can modify user role assignments, and validate that authenticated users cannot escalate their own privileges.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46624 — 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-2024-46624 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