CVE-2025-8913
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 · uneditedOrganization Portal System developed by WellChoose has a Local File Inclusion vulnerability, allowing unauthenticated remote attackers to execute arbitrary code on the server.
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 confidenceThe WellChoose Organization Portal System suffers from a Local File Inclusion (LFI) vulnerability that allows unauthenticated remote attackers to include arbitrary files from the server filesystem, leading to remote code execution. Attackers can exploit this by manipulating file path parameters to traverse directories and execute malicious code, typically by including web shells or sensitive configuration files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< IFTOP_P3_2_1_197CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 installed version of WellChoose Organization Portal SystemLocate the application version information in the system admin panel, about page, or check version files in the webroot directory. Compare against the affected version range: < IFTOP_P3_2_1_197Affected if The installed version is IFTOP_P3_2_1_197 or any version lower than this value
-
Confirm file inclusion functionality is presentReview the application's source code or documentation to identify any file inclusion features, particularly those that accept file path parameters from user inputAffected if The application contains functionality that accepts file paths as parameters without proper validation
-
Locate file path parameters in the applicationIdentify HTTP request parameters that accept file or path values. Common parameter names include 'file', 'path', 'page', 'include', 'template', or similar. Check GET and POST requests.Affected if The application exposes parameters that accept file path values that could be manipulated for directory traversal
-
Check for directory traversal vulnerabilityTest identified file path parameters with directory traversal sequences such as ../../../../etc/passwd or ../../../../windows/win.ini. Observe if the application returns content from outside the intended directory.Affected if The application returns file contents from arbitrary locations on the server when traversal sequences are used
A user is affected if the WellChoose Organization Portal System version is lower than IFTOP_P3_2_1_197 AND the application exposes file path parameters that are vulnerable to directory traversal manipulation.
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.
dbcve · scopedImplement strict input validation and whitelisting for file path parameters, disable directory traversal capabilities, and consider removing or securing the file inclusion functionality entirely if not business-critical.
IFTOP_P3_2_1_197 or later
- Identify the current installed version of the Organization Portal System by WellChoose
- If the current version is lower than IFTOP_P3_2_1_197, obtain the fixed version (IFTOP_P3_2_1_197 or later) from the vendor
- Backup the current installation and database before upgrading
- Apply the upgrade following the vendor's documented upgrade procedure
- Verify the installation and test that the LFI vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-8913 — 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-8913 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