CVE-2024-54448
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 · uneditedThe Automation Scripting functionality can be exploited by attackers to run arbitrary system commands on the underlying operating system. An account with administrator privileges or that has been explicitly granted access to use Automation Scripting is needed to carry out the attack. 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 · moderate confidenceLogicalDOC's Automation Scripting feature contains a command injection vulnerability that allows authenticated administrators or users with explicit scripting access to execute arbitrary operating system commands on the web server. The feature fails to properly sanitize or restrict script inputs, enabling OS-level command execution.
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< 9.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Check LogicalDOC versionNavigate to the administration panel, typically found under 'System' or 'Settings' > 'About' in the LogicalDOC web interface. Alternatively, check the installation directory for a version file or the WAR/webapp manifest.Affected if Installed version is LogicalDOC Logicaldoc below version 9.1
-
Verify Automation Scripting feature is enabledAccess the administration panel and locate the Automation Scripting or Scripting module configuration, typically under 'System' > 'Modules' or 'Automation' settings. Confirm whether the feature toggle or status shows as enabled.Affected if The Automation Scripting feature is currently enabled in the system configuration
-
Identify users with scripting accessIn the administration panel, review user roles and permissions under 'Users' or 'Security' settings. Look for accounts assigned the Administrator role or a specific Scripting/Automation permission grant.Affected if Any user account besides yourself has Administrator rights or explicit Scripting/Automation access granted
You are affected if your LogicalDOC version is below 9.1 AND the Automation Scripting feature is enabled AND at least one user account (potentially compromised or malicious) has administrative or scripting permissions.
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.
dbcve · scoped9.1
Restrict and audit access to the Automation Scripting functionality to only essential personnel, implement strict input validation and command whitelisting for the scripting engine, and apply vendor patches when released. Consider disabling Automation Scripting if not business-critical.
LogicalDOC version 9.1 or later
- 1. Upgrade LogicalDOC installation to version 9.1 or later to remediate the code injection vulnerability in Automation Scripting
- 2. After upgrading, verify the Automation Scripting functionality is working correctly
- 3. Review user accounts and ensure only necessary administrators have access to Automation Scripting functionality
- 4. Follow the principle of least privilege - restrict Automation Scripting access to only those users who absolutely require it
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54448 — 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-54448 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