CVE-2023-25608
Fortinet Fortiap-W2 6.0.0 – 7.0.1
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-25608 is a medium-severity Incomplete Filtering of One or More Instances of Special Elements (CWE-792) vulnerability in Fortinet Fortiap-W2. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-29549
Vulnerability Data
An incomplete filtering of one or more instances of special elements vulnerability [CWE-792] in the command line interpreter of FortiAP-W2 7.2.0 through 7.2.1, 7.0.3 through 7.0.5, 7.0.0 through 7.0.1, 6.4 all versions, 6.2 all versions, 6.0 all versions; FortiAP-C 5.4.0…
more
through 5.4.4, 5.2 all versions; FortiAP 7.2.0 through 7.2.1, 7.0.0 through 7.0.5, 6.4 all versions, 6.0 all versions; FortiAP-U 7.0.0, 6.2.0 through 6.2.5, 6.0 all versions, 5.4 all versions may allow an authenticated attacker to read arbitrary files via specially crafted command arguments.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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 directly require complete input filtering and validation to prevent this class of weakness.
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.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach many but not all filtering defects before downstream use; a bounded remainder (e.g. incomplete coverage of obscure element variants, second-order flows, or non-software system boundaries) can still be exploited.
A.8.26 requires identifying and specifying requirements (incl. resilience against SQL injections, input validation, output controls, and related protections), which can lead to preventing incomplete filtering of special elements, but only reaches a minority slice since it is a requirements-gathering process whose effect depends on downstream implementation by other controls.
A.8.27 mandates security-by-design principles including data validation/sanitization, distrust-external-input, secure architecture reviews against attack patterns, and defense-in-depth; this reaches some but not most instances of incomplete special-element filtering (a code-level neutralization defect), with the bulk left to implementation rigor in A.8.28 or specific testing in A.8.29.
Secure coding standards require complete sanitization of special elements before downstream processing.
Security testing in development and acceptance can detect incomplete filtering but does not itself implement the fix.