What is the CVSS score of EUVD-2026-42158?

EUVD-2026-42158 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.3%.

Which versions of OneBlog are affected by EUVD-2026-42158?

OneBlog V2.3.9 exposes WeChat Official Account authentication credentials via unprotected REST endpoints; publicly available exploit code exists.

How to fix or mitigate EUVD-2026-42158?

Within 24 hours: Identify all OneBlog V2.3.9 deployments in production; immediately rotate WeChat access_token and jsapi_ticket credentials; restrict network access to exposed RestApiController endpoints via firewall rules. Within 7 days: Audit WeChat Official Account activity logs for unauthorized access or integrations; deploy WAF or API gateway rules requiring authentication on sensitive endpoints; verify account recovery options enabled. Within 30 days: Establish upgrade timeline once vendor releases patch; conduct full security audit of WeChat integration architecture.

OneBlog EUVD-2026-42158

| CVE-2026-51937 HIGH

Missing Authentication for Critical Function (CWE-306)

2026-07-07 mitre

GHSA-mmvx-rq8p-h6g9

Authentication Bypass Java N A

7.5

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

vuln.today AI

7.5 HIGH

Unauthenticated network endpoint (AV:N/AC:L/PR:N/UI:N) leaks high-value secrets giving C:H; no direct integrity/availability impact, and Scope kept Unchanged conservatively despite downstream WeChat-account risk.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 08, 2026 - 15:25 vuln.today

CVSS changed

Jul 08, 2026 - 15:22 NVD

7.5 (HIGH)

CVE Published

Jul 07, 2026 - 00:00 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 07, 2026 - 00:00 cve.org

HIGH 7.5

DescriptionCVE.org

An issue in Oneblog V2.3.9 allows a remote attacker to obtain sensitive information via the RestApiController.java, JsApiTicketComponent.java, and the GetAccessTokenComponent.java component

AnalysisAI

Sensitive information disclosure in OneBlog V2.3.9 lets remote unauthenticated attackers retrieve WeChat Official Account secrets - the access_token and jsapi_ticket - through unprotected REST endpoints backed by RestApiController.java, JsApiTicketComponent.java, and GetAccessTokenComponent.java. Because these credentials grant control over the linked WeChat public account, disclosure enables account takeover of the integration rather than just data leakage. Classified CWE-306 (Missing Authentication); a referenced public gist appears to contain proof-of-concept details, though EPSS is low (0.26%, 18th percentile) and it is not listed in CISA KEV.

Technical ContextAI

OneBlog is an open-source Spring Boot (Java) blogging/CMS platform (github.com/zhangyd-c/OneBlog) that integrates with the WeChat Official Account (Weixin) platform. The WeChat API model requires servers to fetch a global access_token (via the Get_access_token endpoint referenced in the CVE) and derive a jsapi_ticket for signing front-end JS-SDK calls; both are long-lived, high-privilege secrets that authorize API operations on the official account. In OneBlog, GetAccessTokenComponent.java obtains the access_token and JsApiTicketComponent.java obtains the jsapi_ticket, and RestApiController.java surfaces this data over HTTP. The root cause is CWE-306 (Missing Authentication for Critical Function): the controller returns these secrets without enforcing any authentication or authorization check, so any client that reaches the endpoint receives credentials intended to remain server-side.

RemediationAI

No vendor-released patch version is identified at time of analysis; tracking is via the upstream issue https://github.com/zhangyd-c/OneBlog/issues/43, so monitor that issue and the OneBlog repository for a fixed release and upgrade as soon as one is published. As immediate compensating controls: place the affected REST API endpoints behind authentication/authorization (require an admin session or API key) since the root cause is missing auth (CWE-306); block or restrict external network access to the endpoints exposing access_token and jsapi_ticket via a reverse proxy or WAF rule so they are reachable only from trusted internal callers (trade-off: may break legitimate front-end JS-SDK signing flows that fetch the ticket, so scope rules to the exact paths); and if the WeChat integration is not used, disable it entirely. Because the leaked access_token/jsapi_ticket are treated as compromised, rotate/refresh the WeChat Official Account credentials (force a new access_token) after remediation. Cross-check the fix against the referenced gist https://gist.github.com/Passwords404/2599df955cdb36b36b9551b5b7809114 to confirm the exposed paths are closed.