# CVE-2026-30689: Missing authorization in Blog.Core

> Unauthorized users can access sensitive administrator account information via the getinfobytoken API interface in Blog.Core.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-x4mm-wg99-32fj

## What is CVE-2026-30689?

CVE-2026-30689 is a medium-severity missing authorization vulnerability in anjoy8 Blog.Core, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control), CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-30689?

It affects 1 product.


Products: Anjoy8 Blog.admin.

## How do I fix CVE-2026-30689?

No fix has been published for CVE-2026-30689 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30689 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30689 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30689 and fix it if it is affected.

What it is: CVE-2026-30689 is a medium-severity missing authorization vulnerability in anjoy8 Blog.Core, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30689 exists.

Affected product: anjoy8 Blog.Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30689/ (Markdown: https://insights.sbomify.com/CVE-2026-30689/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30689
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30689
- OSV: https://osv.dev/vulnerability/CVE-2026-30689

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30689/
Summaries are generated and may contain mistakes; the official description above is the record.