CVE-2025-31411
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in aribhour Linet ERP-Woocommerce Integration linet-erp-woocommerce-integration allows Path Traversal.This issue affects Linet ERP-Woocommerce Integration: from n/a through <= 3.5.12.
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 confidenceA path traversal vulnerability in the Linet ERP-Woocommerce Integration plugin (versions up to 3.5.12) allows attackers to access files outside the web root directory through unsanitized path inputs, potentially exposing sensitive 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:H/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.
-
Verify Linet ERP-Woocommerce Integration plugin is installedCheck your WordPress plugins directory for the Linet ERP-Woocommerce Integration plugin folder, or list installed plugins via wp-admin > PluginsAffected if The plugin folder 'linet-erp-woocommerce-integration' or similar exists in /wp-content/plugins/
-
Determine installed plugin versionOpen the plugin's main PHP file or readme.txt in the plugin folder and locate the version declarationAffected if The reported version is 3.5.12 or lower
-
Identify if file/path input functionality is activeSearch the plugin files for functions handling file paths, file uploads, or path parameters (look for functions like file_get_contents, fopen, include, require with variable inputs)Affected if The plugin contains code that accepts user-supplied path inputs without sanitization checks like basename(), realpath(), or path traversal prevention
-
Check web server file permissionsReview the web server user permissions on directories outside the web root (such as /etc/, /home/, /var/) to determine if the web server process can read sensitive system filesAffected if The web server runs with sufficient privileges to read files outside the public web directory and the plugin path traversal is exploitable
You are affected if the Linet ERP-Woocommerce Integration plugin version is 3.5.12 or lower and the plugin processes unsanitized path inputs that could be manipulated to access files outside the web root.
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 to ensure file paths resolve within expected directories; restrict file access permissions and consider upgrading to a patched version once available.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31411 — 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-31411 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