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

CVE-2026-34893

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 Thegov Core < 2.0.23 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 vulnerability in Thegov Core versions prior to 2.0.23 allows remote attackers to access sensitive files on the server without authentication. The vulnerability stems from improper input validation in file inclusion functionality, enabling attackers to manipulate file path parameters to read arbitrary files.

MitigationUpgrade Thegov Core to version 2.0.23 or later to patch the LFI vulnerability. If immediate upgrade is not possible, implement input validation and path sanitization on all file inclusion parameters, and restrict file system access permissions.

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 Thegov Core installation
    Search for Thegov Core files on the server. Look for the main installation directory, typically named 'thegov' or 'thegov-core', and locate the version file or configuration that states the product version.
    Affected if Thegov Core is installed and the version cannot be determined or is below 2.0.23
  2. Determine installed version
    Locate the version file or metadata within the Thegov Core installation. Common locations include a version.php, package.json, or a configuration file that states the current software version. Compare the version number to the 2.0.23 threshold.
    Affected if The installed version is below 2.0.23 or the version cannot be verified
  3. Verify file inclusion functionality is enabled
    Check if the file inclusion module or feature is active in the Thegov Core configuration. Review the application's configuration files for enabled features related to file handling, includes, or templates.
    Affected if File inclusion functionality is enabled and accessible without authentication
  4. Test for unauthenticated file inclusion endpoint
    Identify and inspect the file inclusion parameters in the application. Look for endpoints or parameters that accept file paths for inclusion, such as 'file', 'path', 'page', or 'include' parameters. Attempt to access these without providing authentication credentials.
    Affected if The file inclusion endpoint accepts unauthenticated requests and allows path manipulation
  5. Check for sensitive file access
    Review server logs and test (in a non-production manner if authorized) whether the file inclusion parameter can be manipulated to access system files such as /etc/passwd, configuration files, or other sensitive resources outside the intended directory.
    Affected if The application allows reading arbitrary files via path traversal in the file inclusion parameter

The environment is affected if Thegov Core is installed with a version prior to 2.0.23 and the file inclusion functionality is exposed and accessible without authentication.

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 Thegov Core to version 2.0.23 or later to patch the LFI vulnerability. If immediate upgrade is not possible, implement input validation and path sanitization on all file inclusion parameters, and restrict file system access permissions.

Recommended fix High confidence

Thegov Core 2.0.23

  1. Create a full backup of the current Thegov Core installation including files and database
  2. Download Thegov Core version 2.0.23 or the latest stable release from the official vendor
  3. Replace all existing Thegov Core files with the new version files
  4. Verify the integrity of the upgraded installation by checking that core files are present and undamaged
  5. Confirm the upgrade was successful by accessing the application and verifying normal functionality
  6. Test that the Local File Inclusion vulnerability is no longer exploitable by attempting to access local files through known vulnerable parameters

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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