CVE-2026-22330
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 · uneditedUnauthenticated Local File Inclusion in Right Way <= 4.0 versions.
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 confidenceUnauthenticated Local File Inclusion (LFI) vulnerability in Right Way software versions 4.0 and below. The flaw allows remote attackers to read sensitive files on the server without authentication via manipulation of file inclusion parameters.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 Right Way software installationLocate the Right Way software installation directory and check for version information files (such as version.php, info.php, or a config file containing version metadata)Affected if The installed version is 4.0 or lower, or if no version file is found but the software is confirmed as Right Way
-
Determine if file inclusion parameters are exposedSearch the application source code for file inclusion functions (include, require, include_once, require_once, fopen with file paths, or similar) and identify parameters that accept user input (GET, POST, or COOKIE parameters)Affected if File inclusion parameters that accept user-supplied input are present and reachable without authentication
-
Verify unauthenticated access to file inclusion endpointsAttempt to access identified file inclusion parameters directly (without authentication cookies or tokens) using a web request tool to confirm they are accessible without loginAffected if The file inclusion endpoints respond without requiring authentication
-
Check for sensitive file exposureTest the file inclusion parameter with path traversal sequences (such as ../../../../etc/passwd or similar) to confirm the LFI vulnerability is exploitableAffected if The application returns contents of files outside the web root when path traversal is used
A user is affected if Right Way software version 4.0 or below is installed AND unauthenticated file inclusion parameters are accessible that allow path traversal to read arbitrary files.
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 dataUpgrade to a version beyond 4.0; implement strict input validation and whitelist-based file access controls on all file inclusion mechanisms; disable PHP functions used for file operations if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22330 — 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-2026-22330 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