Security readout for executives and security teams
Plain-English summary
LogicalDOC’s Automation Scripting feature can let a privileged or specifically authorized account execute arbitrary commands on the document server. Successful exploitation could expose, alter, or disrupt documents and server services. The issue is rated high severity, but the supplied evidence does not establish active exploitation or clearly identify affected and fixed releases.
Executive priority
Treat this as a high-priority privileged-access risk. Promptly inventory LogicalDOC, tighten scripting permissions, and seek authoritative version and remediation guidance. Accelerate incident review where administrative credentials may be exposed, scripting access is broadly assigned, or the service is reachable from untrusted networks.
Technical view
CVE-2024-54448 is a CWE-94 code-injection vulnerability in LogicalDOC Automation Scripting. It is remotely reachable with low attack complexity and no user interaction, but requires high privileges or explicit scripting access. CVSS 4.0 is 8.6, reflecting high confidentiality, integrity, and availability impact on the LogicalDOC web server.
Likely exposure
Exposure is concentrated in LogicalDOC Community or Enterprise deployments where administrators or delegated users can access Automation Scripting. Internet accessibility and compromised privileged credentials would increase risk. The supplied version data lists version "0" with a default unaffected status, so the exact affected release range cannot be determined confidently.
Exploitation context
The source bundle does not report known active exploitation, and CVE-2024-54448 is not listed as KEV in the supplied data. Exploitation requires an administrator account or an account explicitly granted Automation Scripting access. This limits opportunistic attacks but creates serious risk from credential theft, malicious insiders, or excessive permissions.
Researcher notes
The supplied CVSS vector supports network reachability, low complexity, high privileges, no user interaction, and high impact to the vulnerable server. However, the version records are insufficient to identify vulnerable or fixed releases. No supplied evidence confirms public exploitation, exploit availability, a patch version, or downstream-system impact.
Mitigation direction
- Identify LogicalDOC Community and Enterprise deployments and their installed versions.
- Restrict Automation Scripting access to the smallest necessary group of trusted administrators.
- Review privileged accounts and revoke unnecessary or stale scripting permissions.
- Protect administrative access with strong authentication and limited network exposure.
- Check current LogicalDOC and advisory guidance for patches or supported mitigations.
Validation and detection
- Confirm whether Automation Scripting is enabled and who can access it.
- Record each deployment’s edition and exact version for comparison with vendor guidance.
- Review privileged-account activity for unexpected scripting or operating-system command execution.
- Inspect server and application logs for unexplained processes, configuration changes, or service disruption.
- Verify that unnecessary scripting permissions have been removed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-54448 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——BlackDuckVulnerability scoring details
Base CVSS 4.0 score
8.6HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.blackduck.com/blog/cyrc-advisory-logicaldoc.htmlCVE reference, BlackDuck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.