Raw vector
CVSS:3.1/AV:N/AC:L/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-2023-39008 is a critical-severity Command Injection (CWE-77) vulnerability in Opnsense Opnsense. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 12% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A command injection vulnerability tracked as CVE-2023-39008 affects the /api/cron/settings/setJob/ component in OPNsense Community Edition prior to version 23.7 and Business Edition prior to 23.4.2. The flaw, assigned CWE-77 and carrying a CVSS 3.1 score of 9.8, permits unauthenticated remote attackers to supply crafted input that results in execution of arbitrary system commands on the underlying host.
Because the affected endpoint is reachable over the network with no authentication or user interaction required, an attacker can leverage the injection to run commands with the privileges of the OPNsense web-service process, potentially leading to full system compromise including configuration changes, data exfiltration, or persistence.
Public references point to a corrective commit in the OPNsense core repository that addresses the input-handling issue in the cron job settings endpoint; operators are advised to upgrade to the fixed releases. The associated EPSS score remains at 0.0518 with no material increase observed since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-42765
Vulnerability Data
A command injection vulnerability in the component /api/cron/settings/setJob/ of OPNsense Community Edition before 23.7 and Business Edition before 23.4.2 allows attackers to execute arbitrary system commands.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating 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.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.
Application security requirements explicitly call for controls against injection flaws including command injection.
A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.