Skip to main content

waynboot-mall CVE-2026-110126

| EUVDEUVD-2026-98891 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-13 disclosure@vulncheck.com GHSA-rrcp-3x9c-4qr5
5.3
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as mall member
  2. Exploit
    Enumerate sequential address IDs
  3. Execution
    Send POST/DELETE to /address endpoints
  4. Impact
    Overwrite or delete victims' addresses

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Requires a valid, authenticated member account on the waynboot-mall mobile API (PR:L) - exploitation is not possible by a fully unauthenticated attacker. No user interaction and no non-default configuration are needed: the AddressController lacks an ownership/authorization check in the default code path, and address IDs are auto-increment, making victim records trivially enumerable. Limiting factors that reduce real-world risk: the attacker must hold a registered member account, the impact is confined to modifying or deleting shipping-address records (no confidentiality breach or account takeover is described), and only deployments with multiple members present meaningful targets.

Impact

This is a medium-severity authorization flaw (IDOR, CWE-639) whose real-world risk is moderate but bounded. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L, score 5.3) is internally consistent with the description: exploitation is network-reachable and low-complexity via auto-increment ID enumeration, but requires an authenticated member account (PR:L), and impact is limited to integrity and availability of other members' shipping-address records with no confidentiality exposure (VC:N). No EPSS score, no CISA KEV listing, and no weaponized exploit code are present in the input, so there is no signal of active or widespread exploitation; the technique is, however, fully documented in the VulnCheck advisory and the HackMD write-up, which lowers the practical barrier to abuse. Weighing these signals together, this is a legitimate but second-tier priority: not a high-urgency internet-wide threat, but a trivially exploitable integrity issue for any deployment with multiple registered members. One conflict to verify: the input Tag labels this 'Authentication Bypass,' which contradicts both CWE-639 and the description (the attacker is already authenticated) - it is an authorization/ownership bypass, not authentication bypass.

Exploit ScenarioDerived

An attacker registers or uses an existing member account on the waynboot-mall mobile app, then enumerates sequential (auto-increment) address IDs belonging to other members. Because AddressController performs no ownership check, the attacker sends POST /address or DELETE /address/{addressId} requests to overwrite or delete victims' saved shipping addresses - enabling checkout disruption or redirection of shipments. No weaponized exploit code was identified, but the VulnCheck advisory and HackMD write-up document the exact requests needed.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Authenticated members of the waynboot-mall mobile H5 API can overwrite or delete other members' saved shipping addresses, because AddressController in the waynboot-mobile-api module never verifies that the address record being changed belongs to the caller. Exploitation requires only a valid registered member account - no user interaction and no special configuration - and because address identifiers are auto-incrementing, victims are trivially enumerable via POST /address and DELETE /address/{addressId} requests. Rated CVSS 5.3 / assessed CVSS:3.1 5.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L), this is a medium-severity IDOR (CWE-639) whose blast radius is bounded to address-record integrity and availability, with no confidentiality loss or account takeover; confirmed actively exploited? No - no public exploit code has been confirmed, though a technical disclosure writeup exists.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - NVD cites commit 0ef8fa4a951fc1f6d57f3e12e37c31490e886a64 as the remediation reference, but the diff content available for that commit covers AGENTS.md and CLAUDE.md and does not visibly contain an AddressController ownership check, so verify the fix against the repository and the release notes before relying on it as a patched version. The authoritative remediation is to enforce per-object authorization server-side: every address read/write/delete must bind the row lookup to the authenticated member identifier (for example, resolve the record with an added member-id predicate rather than by primary key alone, and return 404/403 instead of mutating when the row does not belong to the caller). Until that change is deployed and verified, compensating controls are: front the mobile API with a gateway/ WAF rule that rejects DELETE /address/{id} and POST /address requests whose target identifier is not present in the caller's own address list (trade-off: requires session-state awareness at the edge, adds latency, and will break legitimate clients if the rule is too strict); rate-limit and alert on sequential or high-cardinality address-id enumeration per member (trade-off: deters bulk abuse but not a single targeted overwrite); shorten address-record retention or soft-delete addresses so destructive writes are reversible (trade-off: schema and cleanup work, plus a brief window where deleted rows remain visible to internal queries); and, if the address feature is not required, disable the mobile address endpoints entirely at the reverse proxy. Note that changing address IDs to non-sequential identifiers is not a fix - it is at best an obfuscation that does not satisfy CWE-639. Full advisory context is at https://www.vulncheck.com/advisories/waynboot-mall-through-2.0.0-idor-via-mobile-address-endpoints.

Affected VersionsENISA

waynboot-mall 0 ≤2.0.0

Affected Packages

euvd waynboot_mall no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic Insecure Direct Object Reference / Authorization Bypass Through User-Controlled Key (CWE-639). waynboot-mall is a multi-module Spring Boot 3.1.4 / JDK 17 e-commerce system using MyBatis-Plus, Spring Security, Redis, RabbitMQ and Elasticsearch; the affected surface is the controller layer of the waynboot-mobile-api module, which serves the H5 mobile mall. Two handlers in AddressController (source lines L44-L67 of the v2.0.0 tree) accept an address identifier supplied entirely by the client: POST /address for update-style writes and DELETE /address/{addressId} for removal. The service/mapper path resolves the row by primary key alone without adding the authenticated member's identifier to the query predicate, so the object reference - not any cryptographic or authorization boundary - determines which record is mutated. Since address primary keys are database auto-increment values, an attacker can walk the integer space and hit other members' rows with high probability. The controller also relies on the authenticated session established by Spring Security, meaning the missing check is a per-object authorization gap layered on top of otherwise functioning authentication.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 5.4 MEDIUM

Authenticated member account required so PR:L; REST IDOR over the network with easy ID enumeration gives AV:N/AC:L; no data disclosure (C:N), only overwrite (I:L) and deletion (A:L) of others' address records.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

waynboot-mall through 2.0.0 contains an insecure direct object reference vulnerability in AddressController that allows authenticated members to modify or delete other members' shipping addresses. Attackers can enumerate auto-increment address ids and send POST /address or DELETE /address/{addressId} requests to overwrite or remove victims' saved addresses.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Rare
small single-author open-source demo e-commerce project, negligible production footprint
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy