Threats affecting pkg:github/MoguBlog

MoguBlog versions up to 6.2 contain a broken access control vulnerability that allows authenticated administrators to move or rename files belonging to other administrators on the network disk. This occurs because certain POST endpoints do not verify the admin_uid before updating file or folder locations. The vulnerability has a medium severity with a CVSS 4.0 score of 5.3.

MoguBlog versions up to 6.2 contain an insecure direct object reference vulnerability that allows authenticated administrators to delete files belonging to other administrators. This occurs because the deletion functions do not verify that the file or folder UID belongs to the requesting administrator, enabling unauthorized deletion of stored objects.

MoguBlog versions up to 6.2 contain an insecure direct object reference vulnerability that allows authenticated administrators to access other administrators' network-disk files. The vulnerability exists because the endpoint POST /networkDisk/getFileList filters files by status, file type, or filePath but does not restrict access by administrator user ID, enabling unauthorized file listing and download URL retrieval.

MoguBlog versions up to and including 6.2 have an information disclosure vulnerability that allows low-privileged front-end users to access sensitive system credentials. By using the getSystemConfig endpoint with a normal reader session token, attackers can retrieve unfiltered configuration data, exposing secret keys for Qiniu and MinIO as well as SMTP mailbox passwords. This vulnerability has a high severity rating with a CVSS score of 7.1.

MoguBlog through 6.2 contains an authorization bypass vulnerability in the POST /pictureSort/getPictureSortByUid endpoint, which omits the @AuthorityVerify annotation required to enforce role-based permissions. Authenticated back-office users without image-category permissions can supply a category uid to retrieve restricted image-category records including metadata such as name, cover file uid, sort order and timestamps.

MoguBlog through 6.2 fails to validate the comment author identity in the POST /web/comment/add endpoint, allowing authenticated users to post comments attributed to any other user. Attackers can supply arbitrary userUid values in the request body to impersonate other accounts including administrators.

MoguBlog through 6.2 fails to authenticate requests to the /web/comment/closeEmailNotification endpoint, allowing unauthenticated attackers to disable email notifications for arbitrary users. Remote callers can modify the startEmailNotification flag in Redis cache for any user identifier to suppress reply notifications without authorization.

MoguBlog through 6.2 contains an authorization bypass vulnerability in the comment deletion endpoint that performs ownership checks against request-body fields instead of the authenticated principal. Attackers can delete arbitrary comments and their replies by supplying comment UIDs and author UIDs obtained from unauthenticated listing endpoints.

MoguBlog through 6.2 exposes Elasticsearch index management endpoints in the mogu_search service without authentication, allowing remote attackers to delete, recreate, or alter the blog search index. Attackers can invoke POST endpoints to wipe the entire search index, delete specific documents, or inject malicious index entries, causing search functionality to return incorrect or no results.

MoguBlog through 6.2 contains an XML external entity injection vulnerability in the WeChat callback handler at POST /wechat/wechatCheck. The WechatRestApi.index() method passes the raw request body to SignUtil.xmlToMap(), which uses an unhardened dom4j SAXReader without DTD or external-entity restrictions. Unauthenticated remote attackers can submit DOCTYPE declarations with external parameter entities to read arbitrary local files or trigger outbound HTTP requests, with resolved entities reflected in error responses.