dbcve.org
CipaceApplication · Cipplanner

CVE-2024-50617

HIGH · 7.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 9.17 or later.
See remediation →
84/100
Remediation priority · High
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
Vulnerabilities in the File Download and Get File handler components in CIPPlanner CIPAce before 9.17 allow attackers to download unauthorized files. An authenticated user can easily change the file id parameter or pass the physical file path in the URL query string to retrieve the files. (Retrieval is not intended without correct data access configured for documents.)

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

Insecure Direct Object Reference (IDOR) and path traversal vulnerability in CIPPlanner CIPAce's File Download and Get File handler components allows authenticated users to download unauthorized files by manipulating either the file ID parameter or by supplying physical file paths directly in the URL query string. The handlers fail to enforce proper data access controls before returning documents.

MitigationUpgrade to CIPPlanner CIPAce version 9.17 or later to obtain the vendor fix. Additionally, review file handler configurations and implement strict access control validation on all file download endpoints.

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
CipaceApplication
Affected:< 9.17

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify CIPPlanner CIPAce installation
    Locate CIPPlanner CIPAce installation directories and confirm the product name in the application metadata or installation folder (commonly found in program files, webapp directories, or the application configuration files).
    Affected if CIPPlanner CIPAce software is present in the environment
  2. Check installed CIPAce version
    Locate and read the version information from the CIPAce application (typically found in an about page, version.xml, or the application's main DLL/version file). Compare the version number against the affected range of versions prior to 9.17.
    Affected if The installed version is lower than 9.17 (for example, 9.16, 9.15, etc.)
  3. Identify File Download and Get File handler endpoints
    Inspect the application's web configuration files (web.xml, application config, or route definitions) to locate mappings for File Download and Get File handler components. Note the URL patterns these handlers respond to.
    Affected if File Download or Get File handlers are defined and exposed in the application configuration
  4. Check for access control configuration on file handlers
    Examine the application's security configuration files, web.xml, or handler-specific configurations to determine whether proper data access controls and authorization checks are defined for file download operations.
    Affected if No explicit access control validation is configured for the file download handlers, or the handlers accept file ID or path parameters without authorization checks
  5. Inspect file download URL patterns for direct object references
    Review application URLs or proxy logs to identify if file download endpoints accept file IDs or physical file paths directly in query string parameters without indirect reference mapping.
    Affected if The file download URLs accept direct file IDs or physical paths in query parameters without additional validation layers

A user is affected if CIPPlanner CIPAce version is installed and is lower than 9.17, and the File Download or Get File handler components are exposed without proper access control enforcement.

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
Upgrade available Upgrade to 9.17 or later
Fixed in 9.17
Interim mitigation

Upgrade to CIPPlanner CIPAce version 9.17 or later to obtain the vendor fix. Additionally, review file handler configurations and implement strict access control validation on all file download endpoints.

Recommended fix Moderate confidence

CIPAce 9.17

  1. Obtain CIPAce version 9.17 or later from CIPPlanner (cipplanner.com)
  2. Follow CIPPlanner's standard upgrade procedure to apply the update
  3. Verify the upgrade was successful by checking the CIPAce version
  4. Test that the File Download and Get File handler components now properly enforce authorization checks

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

Fix this in Cipace Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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