CVE-2022-45368
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 Lenderd 1003 Mortgage Application allows Relative Path Traversal.This issue affects 1003 Mortgage Application: from n/a through 1.75.
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 confidenceThe Lenderd 1003 Mortgage Application versions through 1.75 contains a relative path traversal vulnerability that allows attackers to access files outside the intended web root directory using '../' traversal sequences in file requests.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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 Lenderd 1003 Mortgage Application is installedSearch for Lenderd application files in the web root directory, typically under /lenderd, /1003, or similar application paths. Check for files named 'lenderd', 'lender', 'mortgage', or '1003' in the web server directory structure.Affected if The application is found running on the server
-
Determine the installed versionCheck the application's version by examining version files, about pages, or the application header/footer. Common locations include version.txt, about.php, or the main application configuration file. Compare the version number to the affected range (through 1.75).Affected if The installed version is 1.75 or lower
-
Verify the web file serving functionality is exposedTest if the application exposes a file request endpoint by attempting to access common web paths such as /lenderd/, /1003/, or the application's main URL. Check the web server configuration to confirm the application is accessible via HTTP/HTTPS.Affected if The web interface is publicly or internally accessible
-
Check for path traversal protectionExamine the application's source code or configuration files for input validation logic that handles file paths. Look for functions that sanitize or validate '../' sequences or use canonicalization (realpath, pathinfo) to restrict file access to allowed directories.Affected if No path validation is implemented or the filter can be bypassed
You are affected if Lenderd 1003 Mortgage Application version 1.75 or lower is running with its web file serving functionality exposed and lacking proper path traversal protection.
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 path validation with canonicalization to ensure all file paths resolve within the allowed directory, combined with input filtering and whitelist-based access controls.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45368 — 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-2022-45368 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