moxi624 MoguBlog up to 6.2 Elasticsearch Index Management injection

Summaryinfo

A vulnerability has been found in moxi624 MoguBlog up to 6.2 and classified as critical. This issue affects some unknown processing of the component Elasticsearch Index Management. The manipulation leads to injection. This vulnerability is documented as CVE-2026-89261. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in moxi624 MoguBlog up to 6.2. It has been rated as critical. This issue affects an unknown part of the component Elasticsearch Index Management. The manipulation with an unknown input leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-89261 since 09/11/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/11/2026). MITRE ATT&CK project uses the attack technique T1055 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• moxi624

Name

• MoguBlog

Version

• 6.0
• 6.1
• 6.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion