Quick answers
- Is CVE-2026-109174 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109174 being exploited in the wild.
- How severe is CVE-2026-109174?
- Medium severity, with a CVSS score of 6.5, published 12 October 2026.
- Which products and versions are affected?
- MoguBlog through 6.2.
- Is there a fix for CVE-2026-109174?
- 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-109174 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109174?
- Check whether you run MoguBlog at an affected version. 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 getSystemConfig REST endpoint performs only a token validity check against the Redis user token keyspace but does not verify admin privileges or filter sensitive fields before returning the entire SystemConfig entity. An attacker with any valid end-user session token (obtainable via self-registration) can retrieve Qiniu/MinIO access and secret keys, SMTP server addresses, and email account credentials. The vulnerability is a classic broken access control issue combined with mass assignment, exposing third-party service credentials with no privilege escalation required.
Affected products
- MoguBlog MoguBlog through 6.2
Timeline
- 2026-10-12: disclosed