Security readout for executives and security teams
Plain-English summary
CVE-2026-3287 is a SQL injection issue in youlaitech youlai-mall 2.0.0. A remote authenticated user may manipulate product-list sorting inputs to affect database queries. Public proof-of-concept material is referenced, but there is no KEV listing or cited confirmation of active exploitation.
Executive priority
Prioritize assessment this cycle if you run youlai-mall 2.0.0, especially internet-facing deployments. Public exploit availability raises operational risk, but authentication requirements and medium severity make this less urgent than unauthenticated critical flaws.
Technical view
The flaw affects listPagedSpuForApp in SpuController.java under the App-side Product Pagination Endpoint. Manipulation of sortField or sort can lead to SQL injection. CVSS v2 is 6.5 with network access, low complexity, and authentication required. Vendor response and official remediation are not documented in the provided sources.
Likely exposure
Organizations running youlaitech youlai-mall version 2.0.0 with the app-side product pagination endpoint reachable are potentially exposed. The CVSS vector indicates authentication is required, reducing exposure compared with unauthenticated SQL injection.
Exploitation context
VulDB states a public exploit exists and remote exploitation is possible. The provided data does not show CISA KEV inclusion or confirmed in-the-wild exploitation. Treat public proof-of-concept availability as increasing likelihood of probing against exposed deployments.
Researcher notes
Evidence is primarily from VulDB and CVE records. The vendor reportedly did not respond, and no official patch is named in the provided sources. Avoid assuming other youlai-mall versions are affected unless confirmed by vendor or code review.
Mitigation direction
- Identify whether youlaitech youlai-mall 2.0.0 is deployed.
- Restrict external access to the affected app-side endpoint where possible.
- Review vendor project guidance for patches or safe configuration updates.
- Validate input handling for sortField and sort parameters in local forks.
- Monitor application and database logs for suspicious product pagination requests.
Validation and detection
- Inventory deployed youlai-mall versions and confirm any 2.0.0 instances.
- Locate the App-side Product Pagination Endpoint implementation.
- Review code for parameterized ordering and strict allowlists.
- Check logs for anomalous sortField or sort values.
- Confirm whether compensating access controls require authenticated access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3287 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-348016 | youlaitech youlai-mall App-side Product Pagination Endpoint SpuController.java listPagedSpuForApp sql injectionCVE reference · vdb-entry, technical-description
- VDB-348016 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #758977 | youlaitech youlai-mall 2.0.0 SQL InjectionCVE reference · third-party-advisory
- https://fx4tqqfvdw4.feishu.cn/docx/E1YgdZUApoBU2bxDl37cLgqsnof?from=from_copylinkCVE reference · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.