CVE-2026-53521: CWE-863: Incorrect Authorization in nezhahq nezha
Nezha Monitoring versions from 2.0.14 up to but not including 2.1.0 contain an authorization vulnerability in the PATCH /server/{id} endpoint. This flaw allows the acceptance and persistence of nonexistent ddns_profiles IDs for a member-owned server. If another user later creates a DDNS profile with one of those IDs, the system uses that profile's configuration in the context of the attacker's server. This issue has been fixed in version 2.1.0.
AI Analysis
Technical Summary
CVE-2026-53521 describes an incorrect authorization vulnerability (CWE-863) in Nezha Monitoring, a self-hosted server and website monitoring tool. Between versions 2.0.14 and before 2.1.0, the PATCH /server/{id} API endpoint accepts and stores DDNS profile IDs that do not exist for the member's server. If a different user subsequently creates a DDNS profile with one of these stored IDs, the DDNS worker resolves the stored ID and dispatches updates using the other user's DDNS profile configuration, effectively causing cross-user configuration misuse. This vulnerability was addressed and patched in version 2.1.0.
Potential Impact
The vulnerability allows an attacker to cause the system to use another user's DDNS profile configuration in the context of the attacker's server, leading to incorrect authorization and potential disruption or manipulation of DDNS updates. The CVSS score of 6.4 (medium severity) reflects a network attack vector with low attack complexity, requiring privileges, no user interaction, and impacts integrity and availability with a scope change. There is no indication of confidentiality impact or known exploits in the wild.
Mitigation Recommendations
Upgrade Nezha Monitoring to version 2.1.0 or later, where this vulnerability has been patched. Patch status is confirmed by the vendor advisory stating the issue is fixed in 2.1.0. No additional mitigation steps are indicated.
CVE-2026-53521: CWE-863: Incorrect Authorization in nezhahq nezha
Description
Nezha Monitoring versions from 2.0.14 up to but not including 2.1.0 contain an authorization vulnerability in the PATCH /server/{id} endpoint. This flaw allows the acceptance and persistence of nonexistent ddns_profiles IDs for a member-owned server. If another user later creates a DDNS profile with one of those IDs, the system uses that profile's configuration in the context of the attacker's server. This issue has been fixed in version 2.1.0.
CVSS v3.1
Score 6.4medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53521 describes an incorrect authorization vulnerability (CWE-863) in Nezha Monitoring, a self-hosted server and website monitoring tool. Between versions 2.0.14 and before 2.1.0, the PATCH /server/{id} API endpoint accepts and stores DDNS profile IDs that do not exist for the member's server. If a different user subsequently creates a DDNS profile with one of these stored IDs, the DDNS worker resolves the stored ID and dispatches updates using the other user's DDNS profile configuration, effectively causing cross-user configuration misuse. This vulnerability was addressed and patched in version 2.1.0.
Potential Impact
The vulnerability allows an attacker to cause the system to use another user's DDNS profile configuration in the context of the attacker's server, leading to incorrect authorization and potential disruption or manipulation of DDNS updates. The CVSS score of 6.4 (medium severity) reflects a network attack vector with low attack complexity, requiring privileges, no user interaction, and impacts integrity and availability with a scope change. There is no indication of confidentiality impact or known exploits in the wild.
Mitigation Recommendations
Upgrade Nezha Monitoring to version 2.1.0 or later, where this vulnerability has been patched. Patch status is confirmed by the vendor advisory stating the issue is fixed in 2.1.0. No additional mitigation steps are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T17:30:33.456Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c7c93e617e2d834c6c81a
Added to database: 6/12/2026, 9:39:31 PM
Last enriched: 6/12/2026, 9:55:21 PM
Last updated: 6/12/2026, 10:45:40 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.