Stored XSS in Nezha Monitoring via AlertRule FailTriggerTasks

Publication date: 2026-06-12

Last updated on: 2026-06-15

Assigner: GitHub, Inc.

Description

Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. From version 1.4.0 to before version 2.0.8, a RoleMember can fire other users' cron tasks via AlertRule.FailTriggerTasks (no ownership check). This issue has been patched in version 2.0.8.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-12

Last Modified

2026-06-15

Generated

2026-07-03

AI Q&A

2026-06-13

EPSS Evaluated

2026-07-02

NVD

CVE-2026-47120

Affected Vendors & Products

Vendor	Product	Version / Range
nezha_monitoring	nezha_monitoring	From 1.4.0 (inc) to 2.0.8 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability exists in Nezha Monitoring versions from 1.4.0 up to but not including 2.0.8. It allows a user with the RoleMember role to trigger cron tasks that belong to other users by exploiting the AlertRule.FailTriggerTasks feature. The issue arises because there is no ownership check when firing these tasks, meaning RoleMembers can execute tasks they do not own.

Impact Analysis

The vulnerability can impact you by allowing users with limited privileges (RoleMember) to execute cron tasks of other users without authorization. This can lead to unauthorized actions being performed, potentially disrupting operations or causing unintended side effects. According to the CVSS score of 7.1, the impact is significant with high integrity impact and low availability impact.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade Nezha Monitoring to version 2.0.8 or later, where the issue has been patched.

Hi! I’m here to help you understand CVE-2026-47120. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70