CVE-2025-67980
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in thembay Hara hara allows PHP Local File Inclusion.This issue affects Hara: from n/a through <= 1.2.17.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in thembay Hara hara PHP application. The application improperly validates file paths in include/require statements, allowing attackers to potentially read sensitive local files or achieve code execution through path traversal. The high CVSS score of 8.1 reflects the significant impact of unauthorized file access.
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 the installed version of thembay Hara haraCheck common version files such as version.php, readme.txt, or the main index.php for a version string. Also check any config files that may contain version metadata.Affected if The installed version is 1.2.17 or earlier (any version up to and including 1.2.17 is affected)
-
Locate file inclusion code in the applicationSearch the source code for include, require, include_once, or require_once statements that use variables in the file path argument, particularly looking for parameters like 'page', 'file', 'path', or 'template' in the codebase.Affected if The application uses include/require with dynamic variable paths without strict validation
-
Identify if user input reaches file inclusion functionsTrace the parameter flow from HTTP requests (GET/POST) to the include/require functions. Check if parameters like 'page', 'file', or similar are used directly in include statements without sanitization.Affected if User-supplied input from request parameters flows directly into include/require statements without validation
-
Check for path traversal patterns in the codeSearch the codebase for patterns where user input is concatenated with file paths, such as 'include($page)', 'require($_GET["file"])', or similar constructions that could allow '../' sequences.Affected if The code accepts user input and concatenates it with file paths without filtering path traversal characters
A user is affected if the thembay Hara hara PHP application is version 1.2.17 or earlier AND the codebase contains include/require statements that use unvalidated user input from request parameters.
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 allowlisting for file path parameters, avoid using user input directly in include/require statements, and consider refactoring to use a whitelist of permitted files. If available, upgrade to a patched version beyond 1.2.17.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-67980 — 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-2025-67980 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