CVE-2026-30689: In Blog.Core through bcb4d17, the getinfobytoken API interface contains improper access control that leads to
CVE-2026-30689 is a medium-severity flaw (CVSS 4.3) affecting blog.admin. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
In Blog.Core through bcb4d17, the getinfobytoken API interface contains improper access control that leads to sensitive data exposure. Unauthorized parties can obtain sensitive administrator account information via a valid token, threatening system security. NOTE: Blog.Admin is related front-end code that does not offer an API service.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-07-02 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-30689?
blog.admin: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-30689 being exploited?
CVE-2026-30689 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-30689 affect?
CVE-2026-30689 affects blog.admin. Severity is medium (CVSS 4.3). In Blog.Core through bcb4d17, the getinfobytoken API interface contains improper access control that leads to sensitive data exposure. Unauthorized parties can obtain sensitive administrator account information via a valid token, threatenin
How urgent is CVE-2026-30689?
Priority 25/100. Public exploit reference