CVE-2026-2145VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2145: cym1102 nginxWebUI · Cross Site Scripting

Affects cym1102 nginxWebUISource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
cym1102nginxWebUI	Affected =4.3.0 =4.3.1 =4.3.2 =4.3.3 =4.3.4 =4.3.5 =4.3.6 =4.3.7	Fixed in–
GitHubcym1102/nginxWebUI`pkg:github/cym1102/nginxWebUI`Other threats	Affected =4.3.0 =4.3.1 =4.3.2 =4.3.3 =4.3.4 =4.3.5 =4.3.6 =4.3.7	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-2145 effectively, organizations should implement the following specific measures: 1) Immediately restrict access to the cym1102 nginxWebUI management interface by enforcing network-level controls such as IP whitelisting, VPN access, or firewall rules to limit exposure to trusted administrators only. 2) Employ web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the nginxDir parameter or suspicious input patterns in the /adminPage/conf/check endpoint. 3) Conduct thorough input validation and output encoding on all user-supplied parameters within the Web Management Interface, especially the nginxDir argument, to prevent script injection. 4) Monitor web server and application logs for unusual requests or repeated attempts to exploit the XSS vulnerability. 5) Educate administrators about the risks of clicking untrusted links or opening suspicious emails that could trigger the user interaction needed for exploitation. 6) If feasible, isolate the management interface on a separate network segment or use jump hosts to reduce direct exposure. 7) Engage with the vendor or community to track patch releases or updates addressing this vulnerability and plan for prompt deployment once available. 8) Consider deploying browser security features such as Content Security Policy (CSP) headers to limit the impact of potential XSS attacks. These targeted actions go beyond generic advice and focus on reducing attack surface, preventing exploitation, and detecting attempts until an official patch is released.

Description

A vulnerability was identified in cym1102 nginxWebUI up to 4.3.7. The impacted element is an unknown function of the file /adminPage/conf/check of the component Web Management Interface. Such manipulation of the argument nginxDir leads to cross site scripting. The attack can be executed remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The impact of CVE-2026-2145 on organizations worldwide can be significant, particularly for those relying on cym1102 nginxWebUI for managing their nginx server configurations. Exploitation of this XSS vulnerability could allow attackers to execute arbitrary scripts in the context of the web management interface, leading to session hijacking, credential theft, or unauthorized administrative actions. This could result in unauthorized configuration changes, exposure of sensitive operational data, or further compromise of the underlying infrastructure. Since the vulnerability is remotely exploitable without authentication, attackers can target exposed management interfaces over the internet, increasing the attack surface. The availability of public exploit code further raises the risk of opportunistic attacks. Organizations with lax network segmentation or insufficient access controls on the management interface are particularly at risk. While no widespread exploitation is currently known, the lack of vendor response and patch availability prolongs exposure and risk. The medium severity rating reflects moderate potential damage but highlights the need for timely mitigation to prevent escalation or chaining with other vulnerabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:34 UTC

Technical details

References

Community reviews

Related threats