CVE-2024-53790
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Ogun Labs Lenxel Core for Lenxel(LNX) LMS lenxel-core allows PHP Local File Inclusion.This issue affects Lenxel Core for Lenxel(LNX) LMS: from n/a through <= 1.3.9.
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 confidencePath Traversal vulnerability in Lenxel Core for Lenxel(LNX) LMS allows remote attackers to perform PHP Local File Inclusion (LFI) by manipulating file path inputs with '..' sequences or absolute paths, potentially exposing sensitive system files, configuration data, or enabling arbitrary code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Lenxel (LNX) LMS is installedSearch the web server for Lenxel-related directories, files, or components. Common paths include /wp-content/plugins/lenxel* or similar LMS-related directories. Check for 'lenxel', 'lms', or 'lnx' strings in the codebase.Affected if Lenxel LMS or its Core component is present on the server
-
Determine the installed Lenxel Core versionLocate version files within the Lenxel installation, such as readme.txt, plugin header comments, composer.json, or a version.php file within the lenxel core directories. Inspect the main plugin file for 'Version:' metadata.Affected if The installed version is 1.3.9 or lower (versions prior to the patch)
-
Locate file inclusion code pathsSearch the codebase for PHP file inclusion functions that use user-controlled input: include(), require(), include_once(), require_once(). Look for parameters that accept file paths and could be manipulated with '..' or absolute paths.Affected if File inclusion code exists that references user-supplied input without proper sanitization
-
Identify accessible endpoints leveraging file inclusionReview URL routing and application entry points. Identify which HTTP parameters accept file/path values and are passed to inclusion functions. Test if these parameters are reachable without authentication.Affected if Endpoints exist that pass user-supplied path parameters to PHP inclusion functions without validation
-
Test for path traversal vulnerabilitySend HTTP requests with '..' sequences or absolute paths (e.g., ../../../../etc/passwd or /etc/passwd) to identified endpoints. Observe if file contents are returned or if the application attempts to include the specified file.Affected if The application returns file contents or includes files outside the intended directory when '..' or absolute paths are supplied
A user is affected if Lenxel Core for LNX LMS is installed with version 1.3.9 or lower AND the file inclusion functionality is accessible to attackers.
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.
From vendor dataImplement strict input validation and path sanitization to restrict file inclusions to allowed directories only; upgrade to a patched version beyond 1.3.9 when available from the vendor.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53790 — 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-53790 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