Quick answers
- Is CVE-2026-89263 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89263 being exploited in the wild.
- How severe is CVE-2026-89263?
- Medium severity, with a CVSS score of 5.3, published 11 September 2026.
- Which products and versions are affected?
- MoguBlog MoguBlog through 6.2.
- Is there a fix for CVE-2026-89263?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-89263 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-89263?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass in the comment notification management endpoint. The /web/comment/closeEmailNotification/{userUid} endpoint fails to perform access control checks, permitting unauthenticated attackers to modify the startEmailNotification flag in the Redis cache for arbitrary user IDs. The endpoint is configured with permitAll in WebSecurityConfig and lacks proper user identity validation in CommentRestApi.java. An attacker can harvest real user UIDs from the public /web/comment/getList endpoint and use them to disable notifications for any target user. The fix involves adding authentication checks and authorization logic to verify that only users can modify their own notification settings.
Affected products
- MoguBlog MoguBlog through 6.2
Timeline
- 2026-09-11: disclosed