dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-22326

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Unauthenticated Local File Inclusion in Reprizo <= 1.0.8 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 confidence

Unauthenticated Local File Inclusion (LFI) vulnerability in Reprizo versions 1.0.8 and below allows remote attackers to read arbitrary files on the server by manipulating file path parameters without requiring authentication.

MitigationUpdate Reprizo to a version newer than 1.0.8. If no patch is available, implement strict input validation to block directory traversal sequences (e.g., ../) and restrict file system access controls at the web server level.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Reprizo is installed
    Look for Reprizo application files on the web server (e.g., index.php, config files, or Reprizo-specific directories in the web root)
    Affected if Reprizo application files are present on the server
  2. Determine installed Reprizo version
    Check version files, headers, or application metadata (e.g., version.php, CHANGELOG, or the admin dashboard about page) and compare to 1.0.8
    Affected if The installed version is 1.0.8 or below
  3. Identify exposed file path parameters
    Review application routes and parameters, looking for any endpoint that accepts a file path as a parameter (commonly in include, require, file, path, or page parameters)
    Affected if A parameter accepting file paths is accessible without authentication
  4. Test for directory traversal vulnerability
    Send a request with directory traversal sequences (e.g., ../../etc/passwd) to identified parameters to confirm the LFI exists
    Affected if The application returns contents of files outside the intended directory
  5. Verify the endpoint requires no authentication
    Attempt to access the vulnerable endpoint without providing any credentials or session token
    Affected if The endpoint is accessible without authentication

A user is affected if Reprizo version 1.0.8 or below is running and has an unauthenticated endpoint that accepts file path parameters vulnerable to directory traversal.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Reprizo to a version newer than 1.0.8. If no patch is available, implement strict input validation to block directory traversal sequences (e.g., ../) and restrict file system access controls at the web server level.

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-2026-22326 — 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-2026-22326 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