CWE · MITRE source
CWE-98Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.
In certain versions and configurations of PHP, this can allow an attacker to specify a URL to a remote location from which the product will obtain the code to execute. In other cases in association with path traversal, the attacker can specify a local file that may contain executable statements that can be parsed by PHP.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: full · 3 mapping(s) from 3 framework(s): CAPEC 1 (full) · OWASP-Web 1 (mostly) · ATT&CK 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A05:2025 Injection.
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-68645 KEV | 10.0 | 8.8 | 0.3177 | 2025-12-22 |
CVE-2023-2249 | 8.0 | 8.8 | 0.6081 | 2023-06-09 |
CVE-2023-49084 | 8.0 | 8.0 | 0.6377 | 2023-12-21 |
CVE-2023-6989 | 8.0 | 9.8 | 0.5657 | 2024-02-05 |
CVE-2024-5762 | 8.0 | 8.1 | 0.7160 | 2024-08-21 |
CVE-2014-9186 | 7.0 | 9.8 | 0.0365 | 2019-04-08 |
CVE-2021-21804 | 7.0 | 9.8 | 0.0370 | 2021-07-16 |
CVE-2022-40089 | 7.0 | 9.8 | 0.0198 | 2022-09-22 |
CVE-2022-4446 | 7.0 | 9.8 | 0.0127 | 2022-12-13 |
CVE-2022-4606 | 7.0 | 9.8 | 0.3543 | 2022-12-18 |
CVE-2023-3452 | 7.0 | 9.8 | 0.0562 | 2023-08-12 |
CVE-2023-4488 | 7.0 | 9.8 | 0.0100 | 2023-10-20 |
CVE-2023-5199 | 7.0 | 9.9 | 0.0138 | 2023-10-30 |
CVE-2024-2411 UPD | 7.0 | 9.8 | 0.0154 | 2024-03-29 |
CVE-2024-30849 UPD | 7.0 | 9.8 | 0.0112 | 2024-04-05 |
CVE-2024-3136 UPD | 7.0 | 9.8 | 0.0502 | 2024-04-09 |
CVE-2024-1600 | 7.0 | 9.3 | 0.3109 | 2024-04-10 |
CVE-2024-3806 | 7.0 | 9.8 | 0.0269 | 2024-05-14 |
CVE-2024-33863 | 7.0 | 9.8 | 0.0060 | 2024-05-14 |
CVE-2024-3551 | 7.0 | 9.8 | 0.0069 | 2024-05-17 |
CVE-2024-35629 | 7.0 | 9.6 | 0.0054 | 2024-06-04 |
CVE-2024-36415 | 7.0 | 9.1 | 0.0088 | 2024-06-10 |
CVE-2024-4936 | 7.0 | 9.8 | 0.0103 | 2024-06-14 |
CVE-2024-5577 | 7.0 | 9.8 | 0.0091 | 2024-06-14 |
CVE-2024-4258 | 7.0 | 9.8 | 0.0077 | 2024-06-15 |