dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-32302

HIGH · 8.1 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in gavias Winnex winnex allows PHP Local File Inclusion.This issue affects Winnex: from n/a through <= 1.3.2.

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 confidence

A PHP Local File Inclusion (LFI) vulnerability exists in the gavias Winnex component (version <= 1.3.2). The vulnerability stems from improper control of filenames used in include/require statements, allowing attackers to manipulate file path parameters to include arbitrary PHP files from the local filesystem. This can lead to sensitive data exposure or remote code execution if the attacker can upload files or leverage the inclusion to execute malicious code.

MitigationUpgrade to a patched version of Winnex if available. Otherwise, implement strict input validation on all file inclusion parameters using a whitelist approach, and consider deploying a WAF as a temporary protective measure.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Winnex component installation
    Search your web root directory for folders named 'winnex', 'gavias_winnex', or similar. Common paths include /components/com_winnex/ or /plugins/system/winnex/
    Affected if The Winnex component directory exists on the server
  2. Identify the installed version
    Check for a version file within the Winnex directory. Look for files named version.php, manifest.xml, or a language file containing a version string. Alternatively, search the codebase for a variable holding the version number (e.g., '$this->version' or 'VERSION')
    Affected if The discovered version is 1.3.2 or lower
  3. Examine file inclusion code
    Search the Winnex PHP files for include, include_once, require, or require_once statements that use variables without sanitization. Look for patterns like 'include($variable)' or 'require($_GET[...])' within the component files
    Affected if Unvalidated file inclusion calls using request parameters are found in the code
  4. Identify the vulnerable parameter
    Review the inclusion calls found in step 3 to determine which GET, POST, or REQUEST parameter controls the file path. Common parameter names for LFI include 'file', 'path', 'template', 'page', or 'load'
    Affected if A parameter that can be controlled by an external user is used in the file inclusion function
  5. Test if the parameter accepts traversal
    With a safe, authorized test, attempt to include a known local file (e.g., /etc/passwd on Linux or a configuration file from the same server) using directory traversal sequences like ../../../../etc/passwd in the identified parameter
    Affected if The parameter allows directory traversal and successfully includes files outside the intended directory

If the gavias Winnex component version is 1.3.2 or lower AND user-controlled input reaches an include/require statement without validation, the environment is vulnerable to CVE-2025-32302.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Winnex if available. Otherwise, implement strict input validation on all file inclusion parameters using a whitelist approach, and consider deploying a WAF as a temporary protective measure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32302 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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