Skip to main content

MoguBlog EUVDEUVD-2026-97378

| CVE-2026-109174 HIGH
Incorrect Authorization (CWE-863)
2026-10-12 disclosure@vulncheck.com GHSA-fp5j-hvqq-c3w5
7.1
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register ordinary reader account
  2. Delivery
    Authenticate to obtain session token
  3. Exploit
    Request getSystemConfig with token
  4. Execution
    Receive unfiltered SystemConfig
  5. Impact
    Harvest Qiniu/MinIO/SMTP credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid low-privileged front-end reader session token for the target MoguBlog instance - i.e., the attacker must hold or obtain an ordinary registered reader account, which is typically self-service on public blogs. No elevated privileges, admin access, or user interaction are needed beyond that token, and the getSystemConfig endpoint returns unfiltered SystemConfig over the network. Practical impact is limited to deployments that have actually configured Qiniu/MinIO object storage or SMTP mail, since those are the secrets exposed; an instance with none of these integrations configured leaks correspondingly less. The authentication (reader-account) requirement is the primary limiting factor distinguishing this from a fully unauthenticated leak.

Impact

This is a genuine, easily-actionable confidentiality issue rather than an inflated high-CVSS theoretical. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) indicates a network-reachable attack of low complexity requiring only low privileges and no user interaction, with high confidentiality impact and no integrity or availability impact - consistent with the description of a reader-level account dumping unfiltered SystemConfig. A publicly available POC (poc_oauth_getSystemConfig.py) materially raises practical exploitability: the barrier is reduced to possessing any ordinary reader session token, which on a public blog is typically trivial to obtain via self-registration. Countervailing signals: this is NOT in CISA KEV, so there is no confirmed active exploitation, and no EPSS score was provided in the input to gauge exploitation probability in the wild - treat widespread automated exploitation as unconfirmed. The CWE-863 (incorrect authorization) classification aligns with the described behavior and conflicts with the 'Authentication Bypass' tag: the attacker uses a valid (low-privileged) session, so this is broken authorization/privilege enforcement, not authentication bypass - verify tag before using it for correlation. Net: a real, high-priority credential-exposure bug for anyone actually running MoguBlog, tempered by its niche deployment footprint and the authentication (reader account) prerequisite.

Exploit ScenarioDerived

An attacker self-registers or otherwise obtains an ordinary front-end reader account on a MoguBlog site and authenticates to get a session token. Using the token (as demonstrated by the public POC), they call the getSystemConfig endpoint, which returns unfiltered SystemConfig and exposes Qiniu and MinIO object-storage secret keys plus SMTP mailbox passwords. The attacker then abuses those harvested credentials to access/modify cloud storage buckets and send mail as the victim, pivoting well beyond the blog itself.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 PoC candidate (unverified) No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

Information disclosure in MoguBlog through 6.2 lets any holder of an ordinary front-end reader session token retrieve unfiltered SystemConfig data - including Qiniu and MinIO secret keys and SMTP mailbox passwords - from the getSystemConfig endpoint over the network. The CVSS 4.0 base score is 7.1 (assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N with high confidentiality impact and no integrity or availability impact), and the prerequisite is only a low-privileged authenticated reader account, which many public blogs allow users to self-register. Exploitation status: publicly available exploit code exists (a PoC script targeting the OAuth getSystemConfig path is published), but there is no confirmed active exploitation (no CISA KEV listing), and real-world impact is bounded by whether the deployment has actually configured Qiniu/MinIO storage or SMTP mail, since those are the credentials exposed.

RemediationAI

No vendor-released patch was identified at time of analysis - the available references consist of the VulnCheck advisory, the vulnerable upstream source lines, and a public PoC, with no fixed release or upstream commit provided - so treat the following as compensating controls. First, restrict the getSystemConfig endpoint at the reverse proxy/WAF or in application code so that only administrative sessions can call it, or split the response so non-admin callers receive a masked SystemConfig that omits storage and mail secret fields; the trade-off is that legitimate front-end blog pages or OAuth flows that read non-sensitive config may break and must be re-pointed at a sanitized endpoint. Second, because the exposed values are live credentials, rotate the Qiniu access/secret keys, MinIO credentials, and SMTP mailbox passwords and re-deploy the configuration, accepting the required reconfiguration of storage and mail integrations. Third, if object storage or SMTP is not in use, disable or remove those integration settings entirely to shrink the leaked secret surface, with the caveat that file uploads and outbound email will stop working if later re-enabled without reconfiguration. Additionally, monitor and review access logs for GET requests to the getSystemConfig path from low-privilege reader accounts, since the published PoC (https://github.com/AnkesKasty/cve-request-poc/blob/a7b6d1423555812d8efa26c91c5d0683164b31e5/mogu_blog_v2/poc_oauth_getSystemConfig.py) makes discovery and abuse straightforward for anyone holding a reader token, and consult the advisory at https://www.vulncheck.com/advisories/mogublog-through-6.2-credential-disclosure-via-oauth-getsystemconfig for updates.

Affected VersionsENISA

MoguBlog 0 ≤6.2

Affected Packages

euvd mogublog no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is an authorization failure (CWE-863, Incorrect Authorization) in MoguBlog's mogu_web Spring Boot module: the getSystemConfig handler in com.moxi.mogublog.web.restapi.AuthRestApi (lines ~490-502 of the upstream source) returns the application's SystemConfig object without filtering sensitive fields or enforcing an administrative privilege check. Because the endpoint is reachable by any authenticated front-end reader session - the same class of token issued to ordinary registered comment readers - the object-storage and mail integration secrets stored in SystemConfig (Qiniu access/secret keys, MinIO credentials, SMTP mailbox passwords) are serialized back to the caller. The underlying technology is a Java/Spring MVC REST API backed by a persistence-layer configuration entity; the root cause is that authorization is applied at the session/authentication layer only, not at the object-field level, so a valid low-privilege principal is treated as authorized for a configuration read. No CPE identifiers were supplied in the available data, so exact vulnerable coordinates are limited to the product/version statement MoguBlog through 6.2 and the referenced source file.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 7.1 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Network-reachable endpoint with low complexity, but a valid reader account is required so PR:L; impact is pure credential disclosure, hence C:H with I:N/A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

MoguBlog through 6.2 contains an information disclosure vulnerability that allows low-privileged front-end users to read system credentials via the getSystemConfig endpoint. Attackers can supply an ordinary reader session token to retrieve unfiltered SystemConfig data, exposing Qiniu and MinIO secret keys and SMTP mailbox passwords.

Technical POC Analysis

CWE-863 (Incorrect Authorization), specifically a missing authorization boundary plus absent field projection on a shared read endpoint.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Latest POC

1 PoC candidate from github (unverified)

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

MoguBlog versions through 6.2 are affected by an information disclosure flaw that allows an authenticated low-privileged reader to retrieve sensitive configuration data-including Qiniu and MinIO secret keys and SMTP passwords-from the getSystemConfig endpoint. publicly available exploit code exists, and no vendor-released patch identified at time of analysis. For organizations running public MoguBlog instances with these integrations configured, leadership should prioritize remediation because exposed credentials could enable unauthorized access to cloud storage, email systems, and other services.

Business Impact: High
Compensating Controls

Restrict access to the getSystemConfig endpoint to trusted IPs; disable self-registration; rotate exposed Qiniu/MinIO/SMTP credentials; deploy WAF rules to block exploit attempts; enforce MFA and monitor for unauthorized access.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Low
niche open-source Chinese blog platform, limited enterprise deployment
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

56
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy