VulnerabilityPublished 16 Mar 2026

CVE-2026-4201: glowxq-oj · Unrestricted Upload

Affects glowxq-ojSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

6.9Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
glowxqglowxq-oj	Affected =6f7c723090472057252040fd2bbbdaa1b5ed2393	Fixed in–

AI-suggested

Given the lack of official patches, organizations should implement immediate compensating controls to mitigate this vulnerability. First, restrict access to the Upload function by enforcing network-level controls such as IP whitelisting or VPN-only access to reduce exposure. Implement strict input validation and file type restrictions at the application or web server level to block potentially dangerous file types (e.g., executable scripts, web shells). Employ web application firewalls (WAFs) with custom rules to detect and block suspicious upload attempts. Monitor logs for unusual upload activity or unexpected file types. If possible, isolate the glowxq-oj application environment to limit the impact of a successful exploit. Conduct thorough code reviews to add validation and authentication checks around file uploads. Consider disabling the upload functionality temporarily if not essential. Maintain regular backups and have an incident response plan ready in case of compromise. Engage with the vendor or community for updates and patches. Finally, track threat intelligence sources for emerging exploit trends related to this vulnerability.

Description

A weakness has been identified in glowxq glowxq-oj up to 6f7c723090472057252040fd2bbbdaa1b5ed2393. This vulnerability affects the function Upload of the file business/business-system/src/main/java/com/glowxq/system/admin/controller/SysFileController.java. Executing a manipulation can lead to unrestricted upload. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The unrestricted file upload vulnerability in glowxq-oj can have serious consequences for organizations using this software. Attackers can remotely upload malicious files that may lead to remote code execution, allowing full system compromise. This can result in data breaches, unauthorized access to sensitive information, disruption of services, and potential lateral movement within networks. The absence of authentication and user interaction requirements lowers the barrier for exploitation, increasing the risk of automated attacks. Organizations relying on glowxq-oj for critical business functions or hosting sensitive data face heightened risks of operational disruption and reputational damage. The lack of vendor response and patches further exacerbates the threat, as organizations must rely on their own mitigations. The availability of public exploit code increases the likelihood of widespread exploitation attempts, especially targeting internet-facing instances. Overall, this vulnerability poses a moderate to high risk depending on deployment context and exposure.

Summary

CVE-2026-4201 is a vulnerability identified in the glowxq-oj product, specifically in the Upload function implemented in the SysFileController.java file. The vulnerability arises from insufficient validation or restrictions on file uploads, allowing an attacker to upload arbitrary files without any authentication or user interaction. This unrestricted upload capability can be exploited remotely, potentially enabling attackers to upload malicious files such as web shells or scripts that could lead to remote code execution, data compromise, or further system infiltration. The affected version is identified by a specific commit hash (6f7c723090472057252040fd2bbbdaa1b5ed2393), but due to the lack of versioning in the product, it is difficult to determine the full scope of affected deployments. The vendor was contacted but did not respond, and no official patches or mitigations have been released. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the ease of exploitation (no authentication or user interaction required) but limited scope of impact due to the need for specific conditions to achieve full compromise. Public exploit code is available, increasing the likelihood of exploitation attempts. The vulnerability does not require privileges or user interaction, making it a significant risk for exposed installations. The lack of versioning and vendor response complicates mitigation and detection efforts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Mar 2026, 01:20 UTC

Technical details

References

Community reviews

Related threats