CVE-2025-9990
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-9990 is a high-severity PHP Remote File Inclusion (CWE-98) vulnerability in Wordpress (inferred from references). Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-9990 is a Local File Inclusion (LFI) vulnerability, classified under CWE-98, in the WordPress Helpdesk Integration plugin for WordPress. It affects all versions up to and including 5.8.10 and is exploitable via the portal_type parameter. The flaw enables the inclusion and execution of arbitrary .php files on the server, allowing PHP code execution from those files. The vulnerability has a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating high severity with network accessibility but high attack complexity.
Unauthenticated attackers can exploit this vulnerability remotely without privileges or user interaction. By manipulating the portal_type parameter, they can include arbitrary .php files, leading to PHP code execution. This can bypass access controls, disclose sensitive data, or enable full remote code execution if .php file uploads are possible through other means on the target system.
Mitigation details are available in related advisories and source code references, including the Wordfence threat intelligence report at https://www.wordfence.com/threat-intel/vulnerabilities/id/49a935cc-7b95-4abd-9a4d-c7e14c765863?source=cve, as well as WordPress plugin repository files at https://plugins.svn.wordpress.org/wp-helpdesk-integration/trunk/index.php and https://plugins.trac.wordpress.org/browser/wp-helpdesk-integration/trunk/index.php#L85.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-26999
Vulnerability Data
The 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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing filename restrictions before deployment.
Validating all inputs before they reach include/require statements directly stops untrusted filenames from being used.
Enforcing access authorizations on resources limits what an included file can reach even if a bad name is supplied.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect RFI but does not prevent the weakness by itself.
Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.