dbcve.org
LogicaldocApplication

CVE-2024-54449

HIGH · 8.8 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to 9.1 or later.
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
The API used to interact with documents in the application contains two endpoints with a flaw that allows an authenticated attacker to write a file with controlled contents to an arbitrary location on the underlying file system. This can be used to facilitate RCE. An account with ‘read’ and ‘write’ privileges on at least one existing document in the application is required to exploit the vulnerability. Exploitation of this vulnerability would allow an attacker to run commands of their choosing on the underlying operating system of the web server running LogicalDOC.

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

LogicalDOC contains a path traversal/file write vulnerability in two API endpoints. An authenticated attacker with read/write privileges on any existing document can write arbitrary files with controlled contents to any location on the filesystem, leading to remote code execution.

MitigationRestrict file write operations to authorized directories only by implementing strict path validation and path traversal prevention in the affected API endpoints. Consider adding allowlist-based directory restrictions for document operations.

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
LogicaldocApplication
Affected:< 9.1

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. Determine LogicalDOC version
    Locate the LogicalDOC installation and identify the installed version number (check installation directory, version file, or application startup logs)
    Affected if Version is below 9.1 (versions 9.0 and earlier are affected; version 9.1 and later are NOT affected)
  2. Confirm API endpoints are exposed
    Identify which API endpoints are accessible on the LogicalDOC server (typically at /api/ paths in the web application)
    Affected if The document write API endpoints are exposed and reachable over the network
  3. Verify API authentication is enabled
    Check the API security configuration to confirm that authentication is required for document operations
    Affected if Authentication is not enforced or can be bypassed on the affected endpoints
  4. Check for users with document write privileges
    Review user accounts and roles in the system to identify any authenticated users who have read/write access to documents
    Affected if Any authenticated user has read/write privileges on existing documents
  5. Inspect file write path validation
    Examine the API endpoint configuration or application logs to determine if path traversal validation is implemented for file write operations
    Affected if No path traversal protection or directory restriction is configured on the document write endpoints

You are affected if running LogicalDOC version below 9.1 AND the vulnerable API endpoints are accessible to authenticated users with document write permissions

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.1 or later
Fixed in 9.1
Interim mitigation

Restrict file write operations to authorized directories only by implementing strict path validation and path traversal prevention in the affected API endpoints. Consider adding allowlist-based directory restrictions for document operations.

Recommended fix Moderate confidence

LogicalDOC 9.1 (or latest stable release)

  1. 1. Backup the existing LogicalDOC installation and database before proceeding with any upgrade.
  2. 2. Download LogicalDOC version 9.1 or the latest stable release from the official vendor repository.
  3. 3. Review the official LogicalDOC upgrade documentation for version 9.1 to understand the migration process.
  4. 4. Stop the LogicalDOC application service.
  5. 5. Execute the database migration scripts provided with the 9.1 release if any are required.
  6. 6. Deploy the new version 9.1 application files.
  7. 7. Start the LogicalDOC service and verify the application functions correctly.
  8. 8. Validate that the previously vulnerable API endpoints no longer permit arbitrary file writes.
Caveat Review release notes for version 9.1 to check for any breaking changes in API behavior, database schema modifications, or feature deprecations that may affect existing integrations.

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

Fix this in Logicaldoc 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-54449 — 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-54449 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