Skip to content

Web

CVE-2023-36331

Auth bypass in /member/orderList allows viewing other users' orders by tampering userId.

CVSS
8.2Highscored by CISA
Exploited in the wild
Not knownpublic proof of concept per CISA SSVC; not in CISA KEV
EPSS
0.24%chance of exploitation in the next 30 daystop 85% of scored CVEsFIRST score of 14 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
12 Jan 2026analysed here 13 Jan 2026

Summary

Impact

Unauthorized access to other users' order details via manipulated userId in API; data disclosure.

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • xmall v1.1

Fix and mitigation

Action required

Patch when possible

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation poc, automatable yes, technical impact partialAssessed by CISA 12 Jan 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 12 Jan 2026CISA SSVC assessment: exploitation poc
  2. 12 Jan 2026CVE record last updatedsame day later
  3. 12 Jan 2026Publishedsame day later
  4. 13 Jan 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2023-36331 being exploited?

Not confirmed. CVE-2023-36331 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2023-36331?

CVE-2023-36331 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-36331?

Not known from our data. No patch reference has been recorded for CVE-2023-36331, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2023-36331 affect?

CVE-2023-36331 affects xmall v1.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2023-36331?

Enforce server-side auth; validate userId; restrict order data; audit access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Other links (1)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com