Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-6989 is a critical-severity PHP Remote File Inclusion (CWE-98) vulnerability in Getshieldsecurity Shield Security. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — 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.
The Shield Security – Smart Bot Blocking & Intrusion Prevention Security plugin for WordPress is affected by a local file inclusion vulnerability in all versions through 18.5.9. The flaw exists in the render_action_template parameter and is tracked as CVE-2023-6989 with associated CWEs 98 and 22; it permits an unauthenticated attacker to supply an arbitrary path that results in inclusion and execution of PHP files present on the server.
An attacker with no credentials can send a crafted request over the network to trigger the inclusion, achieving arbitrary PHP code execution. Successful exploitation grants full control over the web server process, enabling actions such as data exfiltration, modification of site content, or installation of persistent backdoors, consistent with the CVSS 9.8 rating reflecting network-accessible attack with high impact on confidentiality, integrity, and availability.
References point to a fix committed in WordPress plugin changeset 3013699. The corresponding plugin update resolves the parameter handling issue, and Wordfence advisory material directs administrators to upgrade beyond version 18.5.9.
The CVE carries an EPSS score that has reached a peak of 0.6979.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-59181
Vulnerability Data
The Shield Security – Smart Bot Blocking & Intrusion Prevention Security plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 18.5.9 via the render_action_template parameter. This makes it possible for unauthenticated attacker to…
more
include and execute PHP files on the server, allowing the execution of any PHP code in those files.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
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.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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 development lifecycle mandates input validation and safe include/require patterns that directly prevent remote file inclusion.
Application security requirements explicitly call for controls against injection and unsafe file operations.
Secure architecture principles reduce attack surface but do not specifically address dynamic file inclusion.
Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.
Information access restriction limits which files an application may read or write.