In Blog.Core, the getinfobytoken API endpoint, as highlighted in the updated description, lacks proper access control, allowing any party with a valid token to retrieve detailed administrator account information. This failure of enforcement of authorization exposes sensitive credentials and compromises confidentiality. The function accepts a bearer token but does not verify administrative privileges before returning data, making the data unintentionally available to unauthenticated users who possess a token. The issue corresponds to CWE-284 and CWE-863.

The vulnerability is present in Blog.Core, developed by anjoy8, in commit ref bcb4d17. The CPE string refers to the related Blog.Admin front‑end application, but the API in question exists in Blog.Core. No specific release versions are enumerated in the CVE data, but any deployment of Blog.Core that includes the GetInfoByToken endpoint without proper access controls is affected. Administrators should verify their deployment includes this endpoint and apply the indicated mitigations.

With a CVSS score of 4.3 the problem is of medium severity and an EPSS score of less than 1% indicates only a very low likelihood of exploitation. The vulnerability is not listed in CISA’s KEV catalog. Attackers must already possess a valid token; if they do, a single call to the endpoint exposes protected credentials. Because the flaw is a token‑based authorization issue, it may lead to further privilege escalation if those credentials are reused.