CVE-2026-89264

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-11. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 11, 2026

Advisory Details (5)

Auto-updated Sep 11, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

MoguBlog through 6.2 Comment Author Spoofing via Request-Body Identity | Advisories | VulnCheck

https://www.vulncheck.com/advisories/mogublog-through-6.2-comment-author-spoofing-via-request-body-identity
generic

GitHub - moxi624/mogu_blog_v2: 蘑菇博客(MoguBlog)，一个基于微服务架构的前后端分离博客系统。Web端使用Vue + Element , 移动端使用uniapp和ColorUI。后端使用Spring cloud + Spring boot + mybatis-plus进行开发，使用 Jwt + Spring Security做登录验证和权限校验，使用ElasticSearch和Solr作为全文检索服务，使用Github Actions完成博客的持续集成，使用ELK收集博客日志，文件支持上传七牛云和Minio，支持Docker Compose...

GitHub - moxi624/mogu_blog_v2: 蘑菇博客(MoguBlog)，一个基于微服务架构的前后端分离博客系统。Web端使用Vue + Element , 移动端使用uniapp和ColorUI。后端使用Spring cloud + Spring boot + mybatis-plus进行开发，使用 Jwt + Spring Security做登录验证和权限校验，使用ElasticSearch和Solr作为全文检索服务，使用Github Actions完成博客的持续集成，使用ELK收集博客日志，文件支持上传七牛云和Minio，支持Docker Compose脚本一键部署。 · GitHub

https://github.com/moxi624/mogu_blog_v2
generic

蘑菇博客 发行版 - Gitee.com

https://gitee.com/moxi159753/mogu_blog_v2/releases
generic

mogu_blog_v2/mogu_web/src/main/java/com/moxi/mogublog/web/restapi/CommentRestApi.java at 025d78c7ac7e19b1abf796fa3cc158d855723d15 · moxi624/mogu_blog_v2 · GitHub

https://github.com/moxi624/mogu_blog_v2/blob/025d78c7ac7e19b1abf796fa3cc158d855723d15/mogu_web/src/main/java/com/moxi/mogublog/web/restapi/CommentRestApi.java
generic

cve-request-poc/mogublog-poc/C12_comment_add_author_spoof.py at master · LinYuanyi1/cve-request-poc · GitHub

https://github.com/LinYuanyi1/cve-request-poc/blob/master/mogublog-poc/C12_comment_add_author_spoof.py

Vendor Advisories for CVE-2026-89264(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-21 00:11 UTCEG score recompute
  2. 2026-09-21 00:11 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 01:58 UTCEG score recompute
  5. 2026-09-20 01:58 UTCGHSA enrichment
  6. 2026-09-19 03:46 UTCEG score recompute
  7. 2026-09-19 03:46 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-18 05:34 UTCEG score recompute
  10. 2026-09-18 05:34 UTCGHSA enrichment
  11. 2026-09-17 19:32 UTCEPSS rescore
  12. 2026-09-17 07:22 UTCEG score recompute
  13. 2026-09-17 07:22 UTCGHSA enrichment
  14. 2026-09-16 14:09 UTCEPSS rescore
  15. 2026-09-16 09:07 UTCEG score recompute
  16. 2026-09-16 09:07 UTCGHSA enrichment
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 10:55 UTCEG score recompute
  19. 2026-09-15 10:55 UTCGHSA enrichment
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 12:37 UTCEG score recompute
  22. 2026-09-14 12:37 UTCGHSA enrichment
  23. 2026-09-13 16:48 UTCEPSS rescore
  24. 2026-09-13 14:17 UTCGHSA enrichment
  25. 2026-09-12 16:05 UTCEG score recompute
Show 6 more
  1. 2026-09-12 16:05 UTCGHSA enrichment
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-11 17:32 UTCEG score recompute
  4. 2026-09-11 16:29 UTCEG score recompute
  5. 2026-09-11 15:34 UTCEG score recompute
  6. 2026-09-11 15:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-89264?
CVE-2026-89264 is a medium vulnerability published on September 11, 2026. 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…
When was CVE-2026-89264 disclosed?
CVE-2026-89264 was first published in the National Vulnerability Database on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89264 actively exploited?
CVE-2026-89264 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-89264?
CVE-2026-89264 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-89264?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-89264, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-89264

Explore →

Is Your Infrastructure Affected by CVE-2026-89264?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs