dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-54374

HIGH · 7.5 CVSS v3.1 Published 2024-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Sabri Sogrid sogrid allows PHP Local File Inclusion.This issue affects Sogrid: from n/a through <= 1.5.6.

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

A path traversal vulnerability in Sogrid versions up to 1.5.6 allows unauthenticated attackers to manipulate file paths in PHP include/require statements, potentially reading sensitive files or achieving code execution through local file inclusion.

MitigationUpgrade to a patched version if available; otherwise, implement strict input validation using basename() and allowlist validation to restrict file path access to intended directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Identify Sogrid installation
    Search for Sogrid-related files in your web root directory, typically under a /sogrid/ folder or check common locations like composer.json, index.php, or version files containing 'sogrid' references.
    Affected if Sogrid software is found installed in the environment.
  2. Check installed Sogrid version
    Locate the version file or composer.json in the Sogrid installation directory and read the version number. Common paths include /sogrid/composer.json, /sogrid/src/Version.php, or check the main index.php for a version constant.
    Affected if The installed version is 1.5.6 or lower.
  3. Identify PHP files handling file includes
    Search the Sogrid source code for PHP files containing include, require, include_once, or require_once statements that accept user input (such as $_GET, $_POST, or direct request parameters) as part of the file path.
    Affected if Files using include/require with unsanitized user-supplied path parameters are found.
  4. Inspect path traversal vulnerability in include statements
    Examine identified include/require files for direct concatenation of user input into the file path without using basename(), realpath(), or allowlist validation. Check if parameters like ?file= or ?page= are passed directly to include statements.
    Affected if User-controlled input is directly used in include/require statements without sanitization.
  5. Verify unauthenticated access to vulnerable endpoints
    Test accessing the identified vulnerable PHP endpoints without authentication. Attempt path traversal payloads such as ../../../../etc/passwd in the suspected parameter to confirm the vulnerability is exploitable.
    Affected if The vulnerable endpoints are accessible without authentication and accept path traversal sequences.

You are affected if Sogrid versions 1.5.6 or lower are installed AND the application contains PHP include/require statements that process user-supplied file paths without sanitization and are accessible to unauthenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version if available; otherwise, implement strict input validation using basename() and allowlist validation to restrict file path access to intended directories.

Recommended fix Moderate confidence

Sogrid version 1.5.7 or later (latest stable release)

  1. 1. Back up the current Sogrid installation and database before making any changes.
  2. 2. Download the latest version of Sogrid from the official repository or source.
  3. 3. Replace the existing Sogrid files with the new version, preserving any custom configurations.
  4. 4. Verify that the path traversal vulnerability is resolved by testing file inclusion functionality.
  5. 5. Review application logs to ensure the upgrade completed without errors.
  6. 6. Test critical functionality of the application to confirm normal operation.
Caveat Review changelog for any breaking changes between 1.5.6 and the new version; custom configurations may need adjustment

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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