CVE-2025-69046
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 WebGeniusLab iRecco Core irecco-core allows PHP Local File Inclusion.This issue affects iRecco Core: from n/a through <= 1.3.6.
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 · high confidencePHP Local File Inclusion (LFI) vulnerability in WebGeniusLab iRecco Core allows attackers to include arbitrary local PHP files via unsanitized input in include/require statements. This can lead to code execution, sensitive data exposure, or server compromise.
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 applicationCheck your web server documentation, source code headers, or installed packages to confirm the application is WebGeniusLab iRecco Core. Look for files named 'iRecco', 'irecco', or products from WebGeniusLab.Affected if The application is WebGeniusLab iRecco Core and the installed version falls within the vulnerable range (check version files, composer.json, or changelogs for the specific version number)
-
Locate PHP file inclusion codeSearch the codebase for PHP files containing 'include', 'require', 'include_once', or 'require_once' statements that use variables from $_GET, $_POST, or $_REQUEST as the file path. Use grep: grep -rn 'include\s*\$' or 'require\s*\$_' across the PHP source directory.Affected if Any PHP file uses include/require with unsanitized user-supplied input from request parameters
-
Inspect the inclusion parameter handlingExamine the identified include/require calls to determine which request parameter controls the file path. Check if the parameter value is sanitized, validated against a whitelist, or used directly in the inclusion function.Affected if The parameter used in include/require is not validated against an allowlist and can be manipulated to include arbitrary local PHP files
-
Verify the attack surfaceTest by attempting to include a known local PHP file using the vulnerable parameter, such as adding '?param=../../../../etc/passwd' or '?param=../../index.php' to the affected URL. Observe if the server includes the file contents or triggers a PHP error revealing the path.Affected if The application allows path traversal or direct file paths in the inclusion parameter without proper validation
You are affected if WebGeniusLab iRecco Core is installed and the application contains PHP include/require statements that use unsanitized request parameters to control which files are loaded.
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 with whitelist approach for any parameters used in include/require statements, and ensure all user-supplied data is properly sanitized before being used in file inclusion functions.
- Consultation2.0 h
- Implementation4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,792.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69046 — 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-69046 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