CVE-2025-9990
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 · uneditedThe WordPress Helpdesk Integration plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 5.8.10 via the portal_type parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.
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 confidenceThe WordPress Helpdesk Integration plugin versions up to 5.8.10 is vulnerable to unauthenticated Local File Inclusion via the portal_type parameter. Attackers can supply a path to arbitrary .php files on the server, causing those files to be included and executed, enabling complete remote code execution.
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 the installed plugin versionAccess the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Helpdesk Integration' or 'Helpdesk' in the list, and note the version number displayed. Alternatively, access the plugin directory via FTP or file manager and open the main plugin PHP file (typically helpdesk-integration.php or similar) to read the 'Version:' header in the plugin comments.Affected if The displayed version number is 5.8.10 or lower.
-
Confirm the plugin is activeIn the WordPress admin under Plugins > Installed Plugins, verify that the Helpdesk Integration plugin shows as 'Active'. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin's main file is listed.Affected if The plugin appears in the active plugins list or is present in the active_plugins array.
-
Locate the vulnerable endpointIdentify if the plugin exposes any public-facing endpoints that handle a 'portal_type' parameter. Common paths include /wp-content/plugins/helpdesk-integration/ or similar. Check the plugin's PHP files for code that uses $_GET, $_POST, or $_REQUEST with a 'portal_type' variable passed to include(), require(), or similar file inclusion functions.Affected if Code exists that includes files based on the portal_type parameter without proper sanitization, and the version is 5.8.10 or lower.
Your environment is affected if the Helpdesk Integration plugin version is 5.8.10 or lower and the plugin is active, as the unauthenticated LFI via portal_type parameter can then be exploited.
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 dataUpdate the plugin to version 5.8.11 or later to remediate this vulnerability.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9990 — 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-9990 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