Cyber Resilience

CVE-2023-39002

XSS in Opnsense ≤ 23.7

Public PoCXSS
Published
09 August 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 6.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.012 66th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2023-39002 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Opnsense Opnsense. Its CVSS base score is 6.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 34% 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.

The vulnerability CVE-2023-39002 is a cross-site scripting flaw in the act parameter of system_certmanager.php, affecting OPNsense Community Edition versions before 23.7 and Business Edition versions before 23.4.2. Classified as CWE-79 with a CVSS 3.1 score of 6.1, the issue stems from insufficient sanitization that allows arbitrary web scripts or HTML to be injected and rendered via a crafted payload.

Attackers without authentication can exploit the flaw by delivering a malicious payload that executes in a victim's browser when the parameter is processed. Because the attack vector requires user interaction and results in changed scope, successful exploitation can achieve limited impacts on confidentiality and integrity, such as script execution that alters page content or accesses session data within the OPNsense web interface.

The referenced OPNsense core commit a4f6a8f8d604271f81984cfcbba0471af58e34dc implements the fix for the input handling defect, and administrators are advised to upgrade to the patched releases. The Logical Trust analysis at the provided URL details the discovery and confirms that the vulnerability is resolved by applying these updates. The associated EPSS score has remained flat at its peak value of 0.2358 with no material increase observed.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A cross-site scripting (XSS) vulnerability in the act parameter of system_certmanager.php in OPNsense Community Edition before 23.7 and Business Edition before 23.4.2 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-39007Same product: Opnsense Opnsense
CVE-2023-44275Same product: Opnsense Opnsense
CVE-2023-39000Same product: Opnsense Opnsense
CVE-2023-39006Same product: Opnsense Opnsense
CVE-2023-44276Same product: Opnsense Opnsense
CVE-2023-25837Shared CWE-79
CVE-2023-22438Shared CWE-79
CVE-2023-27614Shared CWE-79
CVE-2023-47164Shared CWE-79
CVE-2023-49145Shared CWE-79

Affected Assets

opnsense
opnsense
≤ 23.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-79

Penetration testing submits XSS payloads to web applications, detecting cross-site scripting flaws for subsequent remediation.

addresses: CWE-79

Validates web inputs to reject script-related content that could produce XSS.

addresses: CWE-79

Output validation against expected content can reject or sanitize script content in generated web pages, reducing XSS exploitability.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

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.

finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

prevents

Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.

prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

none

Webpage malware scanning and block-listing of known malicious sites reduce the likelihood that reflected or stored script payloads reach a user’s browser.

References