EUVD-2026-42158
GHSA-mmvx-rq8p-h6g9
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
4DescriptionCVE.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.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today