CVE-2026-51925
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 · uneditedA Local File Inclusion (LFI) vulnerability exists in docuForm GmbH Client v.11.11c that allows a remote attacker to execute arbitrary code via the dfm-menu_report.php component. Attackers can exploit this flaw to read arbitrary files on the server, including sensitive configuration files, source code or system files.
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 confidenceA Local File Inclusion (LFI) vulnerability in the dfm-menu_report.php component of docuForm GmbH Client v.11.11c allows remote attackers to read arbitrary files on the server by manipulating file path parameters, potentially exposing sensitive configuration files, source code, and system files.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 docuForm GmbH Client installationSearch the system for docuForm-related directories or files. Check common web root locations for docuForm subdirectories. Look for the application name in installed software listings if available.Affected if docuForm GmbH Client version 11.11c is installed on the system
-
Locate the dfm-menu_report.php componentSearch for the file dfm-menu_report.php within the docuForm installation directory. Use file system search commands like 'find' or directory listing to locate this specific PHP file.Affected if The file dfm-menu_report.php exists in the docuForm installation
-
Determine if the component is web-accessibleCheck if the docuForm web interface is running and the dfm-menu_report.php file is accessible via HTTP/HTTPS requests. Inspect web server configuration for docuForm virtual directories or aliases.Affected if The dfm-menu_report.php component is accessible over the network via a web server
-
Test for path traversal vulnerabilityIf the component is web-accessible, attempt to access known system files through the dfm-menu_report.php parameter (e.g., ../../../../etc/passwd or similar path manipulation). Use a safe, read-only test with a non-sensitive file to confirm the vulnerability exists.Affected if The component allows path traversal and returns file contents when given relative paths outside the intended directory
-
Compare installed version to affected releaseIdentify the exact installed version of docuForm GmbH Client through application metadata, about pages, or version files. Compare against the known affected version 11.11c.Affected if The installed version is 11.11c or falls within the affected version range of the product
A user is affected if docuForm GmbH Client version 11.11c is installed, the dfm-menu_report.php component exists and is web-accessible, and the application allows path traversal in file path 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 path sanitization on the dfm-menu_report.php component to prevent path traversal attacks; restrict file access to allowed directories only.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-51925 — 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-2026-51925 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