CVE-2025-69114
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 MaxiNet <= 1.2.10 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 in MaxiNet versions 1.2.10 and earlier allows remote attackers to read arbitrary files on the server filesystem by manipulating file path parameters without proper sanitization, potentially exposing sensitive configuration files, credentials, and source code.
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 if MaxiNet is installedSearch for MaxiNet installation directories, web root folders, or running processes that match the MaxiNet application name. Check common web application paths or use system package managers if installed via OS packages.Affected if MaxiNet software is found running or installed on the system
-
Determine the installed MaxiNet versionLocate version information in MaxiNet source files (such as version.py, __init__.py, setup.py, or a VERSION file), or check the application's main page/about endpoint for version disclosure.Affected if The discovered version is 1.2.10 or any earlier version of MaxiNet
-
Identify exposed file path parametersReview MaxiNet web routes or API endpoints to locate parameters that accept file paths as input (commonly seen in endpoints involving file viewing, downloading, or template rendering).Affected if The application accepts file path input through URL parameters, form fields, or API requests without requiring authentication
-
Verify lack of input sanitizationTest the identified file path parameters with directory traversal sequences (such as ../../etc/passwd or ..\..\windows\win.ini) and observe if the application returns file contents or exposes file metadata.Affected if The application returns file contents or displays error messages revealing file existence when given traversal sequences, indicating missing sanitization
A user is affected if MaxiNet version 1.2.10 or earlier is installed and the application exposes file path parameters without proper input validation.
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 MaxiNet to a version newer than 1.2.10. If no patched version is available, implement strict input validation to restrict file paths and disable directory traversal characters in the application, or deploy a WAF rule to block LFI attempts.
- 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-69114 — 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-69114 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