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-103539 Overview
CVE-2026-103539 is a missing authentication vulnerability [CWE-287] in ZongXR SuperMarket 1.0.0.0. The flaw resides in the startBuy function of instant-buy/src/main/java/com/supermarket/instantbuy/controller/InstantBuyController.java within the Instant Buy component. An attacker can manipulate the Username argument to bypass authentication controls on the purchase workflow. The attack is executable remotely and requires only low-level privileges. A public exploit has been released, increasing the risk of opportunistic abuse against exposed deployments. The maintainers were notified through a public issue report but have not responded at the time of disclosure.
Critical Impact
Remote attackers can trigger purchase operations under arbitrary usernames by exploiting missing authentication in the Instant Buy controller.
Affected Products
- ZongXR SuperMarket 1.0.0.0
- Instant Buy component (InstantBuyController.java)
- Deployments exposing the startBuy endpoint over the network
Discovery Timeline
- 2026-10-01 - CVE-2026-103539 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-103539
Vulnerability Analysis
The vulnerability affects the startBuy function inside the InstantBuyController Java class of the SuperMarket project. The controller processes buy requests but does not verify that the caller is authenticated as the user identified by the Username parameter. By supplying an arbitrary value for Username, a remote attacker can invoke the purchase workflow in the context of another account.
The weakness is classified under [CWE-287: Improper Authentication]. Because the request originates over the network and relies solely on a client-supplied identifier, impersonation is possible without session validation or server-side identity checks. Public references to the issue are available on the GitHub SuperMarket Project and in GitHub Issue #30.
Root Cause
The startBuy handler trusts the Username request parameter as the authoritative identity for the operation. The controller lacks server-side session binding or token validation that would tie the request to an authenticated principal. This design makes authentication a client-controlled value rather than a server-enforced property.
Attack Vector
An attacker sends a crafted HTTP request to the Instant Buy endpoint with a chosen Username value. No prior credentials for the target account are required beyond the ability to reach the endpoint. Exploitation can be automated against any exposed instance of SuperMarket 1.0.0.0, and a public proof-of-concept has been published through VulDB CVE-2026-103539.
// No verified exploit code is published in this advisory.
// See the referenced VulDB and GitHub issue entries for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-103539
Indicators of Compromise
- HTTP requests to the startBuy endpoint containing Username values that do not match the authenticated session user.
- Repeated purchase requests originating from the same source IP but referencing multiple distinct usernames.
- Application log entries showing successful startBuy invocations with no corresponding login event for the referenced account.
Detection Strategies
- Instrument the InstantBuyController to log the authenticated session identity alongside the supplied Username parameter, then alert on mismatches.
- Deploy web application firewall rules to flag requests to the Instant Buy path lacking a valid session cookie or authentication header.
- Correlate order creation events with authentication events to identify purchases without a preceding login.
Monitoring Recommendations
- Monitor outbound order confirmations for accounts that show no recent interactive session activity.
- Track anomalous spikes in startBuy request volume per source IP or user agent.
- Review access logs for the Instant Buy endpoint on a recurring basis until a vendor patch is available.
How to Mitigate CVE-2026-103539
Immediate Actions Required
- Restrict network access to the SuperMarket application, limiting exposure of the Instant Buy endpoint to trusted networks or authenticated reverse proxies.
- Enforce authentication at the reverse proxy or API gateway layer so that unauthenticated requests to startBuy are rejected before reaching the application.
- Audit application logs for suspicious use of the startBuy endpoint across arbitrary usernames.
Patch Information
At the time of publication, the ZongXR SuperMarket maintainers have not released a fix. The issue was reported through GitHub Issue #30 without response. Monitor the GitHub SuperMarket Project for future commits that add server-side identity enforcement to InstantBuyController.startBuy.
Workarounds
- Modify the application to derive the acting user from the server-side session rather than the Username request parameter.
- Add a Spring Security filter or interceptor that validates session identity against the submitted Username value and rejects mismatches.
- Disable the Instant Buy feature until the controller enforces authentication correctly.
# Example reverse proxy rule to require authentication header for the Instant Buy endpoint
location /instant-buy/ {
if ($http_authorization = "") {
return 401;
}
proxy_pass http://supermarket_backend;
}
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

