Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-100192 Overview
CVE-2026-100192 is a missing authentication vulnerability [CWE-306] in X-SpringBoot through version 6.0. The GET /application/manager/select endpoint returns application records containing appKey and appSecret credentials without requiring authentication or applying field filtering. Unauthenticated remote attackers can enumerate tenant application credentials over the network. Those credentials grant access to the platform's SMS-sending functionality, allowing attackers to dispatch arbitrary SMS messages through any tenant's SMS provider. This enables SMS bombing campaigns and brand impersonation against downstream recipients, while shifting SMS costs onto the victim tenant.
Critical Impact
Unauthenticated attackers can harvest appKey and appSecret values from any X-SpringBoot deployment through 6.0 and abuse them to send arbitrary SMS traffic through tenant SMS providers.
Affected Products
- X-SpringBoot through version 6.0
- The XApplicationController endpoint GET /application/manager/select
- Any tenant SMS provider integrated with an affected X-SpringBoot deployment
Discovery Timeline
- 2026-09-25 - CVE-2026-100192 published to the National Vulnerability Database (NVD)
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-100192
Vulnerability Analysis
X-SpringBoot is an open-source Spring Boot management framework. The XApplicationController class exposes an application lookup endpoint intended for administrative use. The handler at GET /application/manager/select returns the full application entity, including the appKey and appSecret fields used to authenticate requests against tenant SMS integrations. The endpoint neither enforces authentication nor strips sensitive fields from the response payload. Any network client that can reach the application can enumerate every application record and extract its credentials. Those credentials then authorize SMS dispatch calls to the configured SMS provider, bypassing the platform's intended authorization model.
Root Cause
The root cause is Missing Authentication for Critical Function [CWE-306]. The controller method at lines 59–64 of XApplicationController.java returns the raw entity without an authentication filter, authorization check, or data transfer object that would redact appSecret. Credentials that should be treated as server-side secrets are serialized directly into the HTTP response.
Attack Vector
Exploitation requires only network reachability to the application. An attacker issues an unauthenticated GET request to /application/manager/select and parses the JSON response to recover appKey and appSecret pairs. The attacker then invokes the platform's SMS sending API using the harvested credentials to send attacker-chosen SMS content through the victim tenant's provider. A public proof-of-concept is available in the GitHub PoC for CVE-Request repository. See the VulnCheck Advisory on X-SpringBoot for a detailed write-up and the vulnerable XApplicationController code on GitHub.
// No verified exploit code is reproduced here. Refer to the linked PoC
// and VulnCheck advisory for request/response details.
Detection Methods for CVE-2026-100192
Indicators of Compromise
- Unauthenticated GET requests to /application/manager/select from external or unexpected source IP addresses.
- HTTP responses from that endpoint containing appKey and appSecret JSON fields leaving the application.
- Spikes in outbound SMS volume or SMS provider billing that do not correlate with legitimate application activity.
- SMS delivery logs referencing recipients, templates, or sender IDs that no tenant workflow authorized.
Detection Strategies
- Create a web application firewall (WAF) or reverse-proxy rule that alerts on any request matching GET /application/manager/select without a valid authenticated session.
- Inspect application access logs for high-frequency enumeration of the /application/manager/* path tree.
- Correlate SMS provider API call volume against baseline tenant usage to detect credential abuse originating from attacker infrastructure.
Monitoring Recommendations
- Forward X-SpringBoot access logs and SMS provider delivery logs into a centralized analytics pipeline for correlation.
- Alert on any outbound HTTP response body that contains appSecret as a JSON key leaving the application tier.
- Monitor for authentication-less responses with HTTP 200 status on administrative endpoints under /application/manager/.
How to Mitigate CVE-2026-100192
Immediate Actions Required
- Restrict network exposure of the /application/manager/select endpoint to trusted administrative networks until a code fix is deployed.
- Rotate all appKey and appSecret values for every tenant application in affected deployments, assuming prior exposure.
- Contact the SMS provider to revoke or rate-limit credentials that may have been harvested, and review recent SMS billing for anomalies.
Patch Information
At the time of publication, no vendor patch is referenced in the NVD entry for CVE-2026-100192. Monitor the upstream X-SpringBoot repository and the VulnCheck advisory for an official fix. Any custom patch should add an authentication filter to the controller, enforce role-based authorization, and return a data transfer object that omits appSecret from serialization.
Workarounds
- Place the application behind a reverse proxy that requires authentication for all /application/manager/* routes.
- Add a Spring Security filter chain rule that denies anonymous access to /application/manager/select.
- Introduce a response-side projection or @JsonIgnore annotation on the appSecret field so the credential is never serialized to clients.
- Apply strict egress controls and rate limits on SMS provider API calls to contain abuse if credentials are already exposed.
# Example Spring Security configuration snippet to deny anonymous access
# to the vulnerable endpoint path
http
.authorizeHttpRequests(auth -> auth
.requestMatchers("/application/manager/**").authenticated()
.anyRequest().permitAll()
)
.httpBasic(Customizer.withDefaults());
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

