FeriproApplication · Mecodia

CVE-2024-41517

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-02
Fix available
A fix is available. Upgrade to after 2.2.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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
An Incorrect Access Control vulnerability in "/admin/benutzer/institution/rechteverwaltung/uebersicht" in Feripro <= v2.2.3 allows remote attackers to get a list of all users and their corresponding privileges.

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 · moderate confidence

Feripro v2.2.3 and prior contains an incorrect access control vulnerability in the administrative rights management endpoint '/admin/benutzer/institution/rechteverwaltung/uebersicht'. The endpoint fails to properly enforce authentication or authorization checks, allowing unauthenticated or unauthorized remote attackers to directly access the user privilege overview page and enumerate all system users along with their assigned privileges.

MitigationImplement proper authentication and role-based access control (RBAC) checks on the affected administrative endpoint to ensure only authorized administrative users can access the user rights overview functionality.

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
FeriproApplication
Affected:<= 2.2.3

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Check installed Feripro version
    Locate the Feripro installation and identify the version number from the application metadata, configuration files, or about page. Common locations include the installation directory, version info files, or the application's main interface.
    Affected if The installed version is 2.2.3 or any prior version (anything <= 2.2.3).
  2. Verify the vulnerable endpoint exists
    Check if the application exposes the path '/admin/benutzer/institution/rechteverwaltung/uebersicht' by attempting to access it via HTTP/HTTPS request without providing any authentication credentials.
    Affected if The endpoint responds with HTTP status 200 or returns content, indicating it is accessible.
  3. Test authentication enforcement on the endpoint
    Send an unauthenticated request to the endpoint and examine the response. Compare the behavior to accessing a known protected administrative page that properly requires login.
    Affected if The endpoint returns user privilege data, user lists, or administrative content without requiring login credentials (no redirect to login, no 401/403 error).
  4. Confirm user enumeration is possible
    Inspect the response from the unauthenticated request to the vulnerable endpoint. Look for arrays or lists of system users, their usernames, and associated privilege/role assignments.
    Affected if The response contains enumerated user accounts with their assigned privileges or roles, indicating the access control failure is exploitable.

A user is affected if they are running Feripro version 2.2.3 or prior AND the administrative endpoint '/admin/benutzer/institution/rechteverwaltung/uebersicht' is accessible without authentication, returning user privilege data.

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
Upgrade available Upgrade to a release after 2.2.3
Interim mitigation

Implement proper authentication and role-based access control (RBAC) checks on the affected administrative endpoint to ensure only authorized administrative users can access the user rights overview functionality.

Fix this in Feripro 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 the upgrade done

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-2024-41517 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41517 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